deploy_events

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

No annotations provided, so description carries full burden. It indicates a read operation ('Fetch'), returns same events as deploy tool, and implies historical data. No mention of destructive or rate-limiting behavior, but the description adequately conveys safety.

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?

Two sentences: first defines purpose and resource, second adds usage context and return shape. Front-loaded, no fluff, every sentence earns its place.

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?

No output schema, but description explains return value (same DeployEvent shapes). It covers the core purpose and usage scenario. Missing explicit indication of whether result is a list or stream, but sufficient for a fetch tool with two parameters.

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%, so baseline is 3. Description adds minor context like 'apikey-gated endpoint' for project_id, but mostly repeats schema descriptions (e.g., operation_id must start with 'op_'). Limited added value over schema.

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?

Description uses specific verb 'Fetch' and resource 'recorded phase-event stream for a deploy operation'. It clearly distinguishes from sibling 'deploy' tool which emits inline events, and mentions the return shape aligns with deploy tool.

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?

Description states it is useful for inspecting deploys after the fact, especially those not observed directly or resumed from another process. This provides clear when-to-use context, though it does not explicitly list alternatives or non-use cases.

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