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

Annotations already declare readOnlyHint=true, so the safe-read nature is covered. The description adds the Forge v2 endpoint mapping (GET /orgs/{organization}/servers/{server}), which is useful context, but says nothing about what 'details' contains or error 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 tightly front-loaded sentences with zero filler: purpose first, endpoint provenance second. Nothing is wasted and the key action leads.

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?

There is no output schema, so the description carries the burden of telling the agent what is returned, yet 'details' is left undefined. Read safety is covered by annotations, but the lack of any return-value shape leaves a real gap for a retrieval tool.

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%, so the schema already documents both parameters with source hints. The description adds only the endpoint template showing where organization and server map in the path, a marginal addition over structured data. 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 states a specific verb (Get) and resource (a single server's details), clearly distinguishing it from the bulk forge_list_servers sibling by emphasizing singularity. It does not, however, name the sibling or scope the retrieval further, so sibling differentiation is only implied.

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 only implied: 'a single server's details' suggests the singular counterpart to forge_list_servers, but there is no explicit when-to-use, when-not, or named alternative. An agent can infer the intent but must do the routing itself.

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