Retrieve deploy

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. Description adds the specific API endpoint (GET /services/{serviceId}/deploys/{deployId}), but does not elaborate on response format or other behavioral details. Acceptable but not extra informative.

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?

Description is short (two sentences) but first sentence is redundant ('Retrieve deploy.'). Second sentence combines purpose and API call. Could be more efficient by merging.

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?

For a simple retrieve operation with 2 parameters and no output schema, the description explains what it does and the API call. However, it does not mention the format or structure of the returned deploy details, which could be helpful without an output schema.

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 covers both parameters with descriptions. Description adds no new meaning beyond stating 'for a particular service' and 'particular deploy', which is already clear from parameter names and 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 tool retrieves details of a specific deploy for a specific service. Specifies verb (retrieve), resource (deploy details), and context (service). Distinguishes from sibling retrieve tools by focusing on deploys.

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?

No guidance on when to use this tool vs alternatives like render_list_deploys or render_retrieve_service. No mention of when not to use it or prerequisites.

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