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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the Forge v2 REST endpoint (GET /orgs/{organization}/servers/{server}/sites/{site}/deployments/{deployment}), which helps correlate with API docs, but says nothing about auth requirements, error cases, or pagination behavior.

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?

Two sentences, front-loaded with the purpose and followed by the endpoint mapping. Nothing wasted and no filler.

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 single-resource read tool with full schema coverage and readOnlyHint annotations, the description covers what is needed to select and call it. Return shape is unspecified and no output schema exists, but 'details' is a reasonable signal for a get-by-id call.

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%, so all four parameters are already documented in the schema, establishing a baseline of 3. The description's endpoint template loosely maps the four path params, adding marginal value but no syntax or format detail 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?

States a specific verb and resource: 'Get a single deployment's details', which is unambiguous. It doesn't explicitly differentiate itself from close siblings like forge_get_deployment_status or forge_get_deployment_log, but 'a single deployment's details' implicitly contrasts with the list/status/log variants.

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 the phrase 'a single deployment's details', but there is no explicit when-to-use guidance and no mention of when to prefer forge_get_deployment_status or forge_get_deployment_log instead. Adequate but with a clear gap.

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