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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description does not need to restate safety. It adds the 'currently published' constraint, which is useful behavioral context. However, it does not mention behavior for invalid/unknown IDs or what happens if the crane is not currently published.

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, efficient sentence with no filler. The key constraint ('currently published') and lookup method ('public ID') are front-loaded and immediately actionable.

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 retrieval tool with one required parameter and strong annotations, the description covers the essential invocation context. It does not explicitly describe the return value or error cases, but 'Get one... crane' reasonably implies a crane object is returned, and annotations cover safety and idempotency.

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 schema provides only 'id: string, minLength 1' with no description, so the description's mention of 'public ID' adds necessary meaning. This is enough for an agent to understand that the required parameter is the crane's public identifier, compensating for the 0% schema description coverage.

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 uses a specific verb ('Get') and a specific resource ('one currently published Gkmex crane by its public ID'), which clearly distinguishes it from list_cranes and compare_cranes. An agent can immediately understand this is a single-record fetch by ID.

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 phrasing 'currently published' and 'by its public ID' gives clear context for when to use this tool: when the agent has a public ID and needs the current published crane. It does not explicitly name alternatives or exclusion conditions, but the usage context is reasonably clear.

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