deployment

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

Explains cancel behavior on terminal deployments (no error, specific return object), default masking of secrets, and caution against persisting revealed secrets. Annotations only have openWorldHint: true, so description adds significant transparency.

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?

Concise and front-loaded with actions. Information about cancel behavior and reveal adds value. Could be slightly more structured, but overall efficient.

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?

Given the output schema exists, the description need not cover return values. It covers all actions, edge case behavior, and security advice, fully meeting the tool's complexity.

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?

All parameters are described in the schema (100% coverage), so the description adds marginal value. It reinforces the reveal warning and cancel behavior but does not elaborate on other parameters beyond 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?

The description clearly states three actions: list deployments, get details (including status, commit, timestamps, optional logs), and cancel in-flight deployments. This differentiates the tool from siblings like database, project, system, etc.

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?

Provides clear usage for each action (list, get, cancel) and a security caution about reveal. Could be slightly more explicit about when not to use, but the action constraints and sibling context suffice.

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