get_deployment

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

No annotations are provided, so the description must convey behavior. 'Get' implies a read-only, non-destructive operation, which is clear. However, it does not disclose error handling (e.g., 404 if not found) or specify what 'details' include (e.g., status, timestamps), leaving room for uncertainty.

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, concise sentence, front-loaded with the action and resource. There is no filler or redundant information, making it efficient and easy to parse.

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 tool with one required parameter, no output schema, and no annotations, the description is mostly sufficient. It clearly indicates the purpose, and the schema covers the parameter. However, adding a note about expected response or related tools (e.g., list_deployments) would enhance completeness, so it falls short of a 5.

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?

The input schema fully documents the only parameter (deploymentId) with a description ('The deployment ID'). The tool description adds no extra semantics beyond referring to 'a specific deployment', and with 100% schema coverage, the baseline of 3 applies.

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 details for a specific deployment, using a specific verb and resource. It distinguishes from siblings like list_deployments (which lists all) and get_deployment_logs (which retrieves logs), but 'details' is somewhat vague without enumerating fields.

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?

Usage is implied by the name and description: use when you have a deployment ID and need details for that deployment. There is no explicit guidance on when to use it versus alternatives, nor any exclusions or references to sibling tools.

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