get_event_flow

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions chronological ordering and scope (all events with the flow key), but lacks details on pagination, error handling when flow key doesn't exist, or whether it's purely read-only. It is adequate but not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured sentence that front-loads the core purpose. Every word contributes meaning, with no fluff. It is appropriately sized for the tool's simplicity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema, and the description does not describe the structure of returned events (e.g., fields, pagination). For a tool that retrieves events, additional context on what each event contains or limits would improve completeness. The description is sufficient for a basic understanding but leaves gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (only flowKey, with description 'Flow key (case-insensitive)'). The tool description adds value by specifying the expected format: 'flow:<key> tag', which clarifies the convention beyond the schema's description. This provides useful context for the agent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves all events sharing a flow key, chronologically ordered, providing a full timeline of a named flow (e.g., release, incident). The verb 'get' and resource 'events' with a specific filter (flow key) are precise, distinguishing it from generic sibling tools like 'timeline' or 'query_events'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the tool does but provides no explicit guidance on when to use it vs. alternatives. It implies usage when a flow key is known, but does not mention scenarios where one would prefer other timeline or event tools, nor does it give exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.