deploy_events

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

No annotations exist. Description implies it's a read-only fetch but does not disclose auth requirements, error behavior, or rate limits. It is clear it returns event shapes similar to deploy.

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?

Three sentences, front-loaded with main action, no redundant information. Each sentence adds value.

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 type (DeployEvent shapes). Use cases are covered. Minor omission: no mention of ordering or pagination for the event stream.

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 parameters are already documented. The description adds context about operation_id being from a prior deploy call but does not provide new semantics beyond the 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 clearly states the verb 'fetch' and resource 'recorded phase-event stream for a deploy operation'. It distinguishes from sibling tools like deploy and deploy_resume by specifying it's for after-the-fact inspection.

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 provides explicit use cases (inspecting a deploy after the fact, for observers or resumption) but does not explicitly state when not to use or compare to alternatives like deploy_list or deploy_release_get.

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