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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds the HTTP endpoint (GET /...), which provides some additional context about the API structure. It does not describe return format or other behaviors, but the annotation covers the safety profile adequately.

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, zero waste. The purpose is first, followed by the API path. Every word earns its place; highly 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?

For a simple get tool with four required string params and no output schema, the description is sufficient. It tells the agent what it does and the endpoint pattern. Could be enhanced by mentioning what is included in 'details' but not strictly necessary given the tool's name and simplicity.

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 coverage is 100% with each parameter described (e.g., 'Site id.'). The description does not add any extra meaning beyond the schema; it only provides the endpoint template. Baseline 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 'Get a single deployment's details', using a specific verb and resource. It distinguishes itself from siblings like forge_list_deployments (list vs single) and forge_get_deployment_status (specific detail vs details) by implication.

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 does not explicitly state when or when not to use the tool, nor does it name alternatives. However, the context and sibling names make it clear that this tool is for fetching a single deployment's details, and it is straightforward. A minor gap in explicit guidance, but adequate.

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