get_deployment

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get details' implies a read-only operation, but it does not describe what fields are returned, whether any permissions are required, or how the response is structured. The lack of an output schema further compounds this gap.

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, front-loaded sentence with no wasted words. It immediately conveys the purpose without any fluff, making it easy to scan and understand. Concise and well-structured.

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?

The tool is relatively simple with only two required parameters and clear schema descriptions, but the lack of an output schema means the description must clarify what 'details' includes, which it does not. For an agent selecting and invoking this tool, the absence of return-value information is a notable gap, though the core purpose is clear.

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 description coverage is 100%: both 'repository' and 'deployment_uuid' have descriptive text in the schema. The description adds no additional parameter semantics beyond what the schema already provides, so the baseline of 3 is appropriate.

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's function with a specific verb ('Get') and resource ('details of a specific deployment'), distinguishing it from the sibling tool 'list_deployments' which lists deployments rather than fetching one. The phrase 'specific deployment' implies a targeted single-resource retrieval.

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?

The description implies usage when you have a deployment UUID and need details, but it does not explicitly state when to use this tool instead of alternatives like list_deployments. No when-not-to-use guidance or alternative tool names are mentioned, leaving the choice somewhat implied.

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