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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, and the description adds only the HTTP endpoint path. It does not mention what happens if the id does not exist, whether the call requires account scoping, or anything about the response shape, so it adds little beyond structured data.

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 short fragments, front-loaded with the resource and cardinality, with no filler. The trailing 'GET /locations?id=.' is a slightly awkward truncation but costs almost nothing.

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 one-parameter read tool with full schema coverage, annotations, and no output schema, this is minimally sufficient to call correctly. It stops short of describing error behavior or how ids are discovered, which an agent would still need in practice.

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 'location_id' documented as the Papershift location id, and the description corroborates that a single id is the input. No added syntax, sourcing guidance (where to obtain ids), or format detail beyond the schema, so baseline 3 applies.

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 the resource (location) and that it returns exactly one by id, which is enough to distinguish it from the sibling papershift_list_locations. The verb is only implied by the name and the 'GET /locations' fragment rather than spelled out, keeping it short of a 5.

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?

There is no explicit statement of when to use this tool versus papershift_list_locations, and no prerequisite or failure conditions are given (e.g. what happens for an unknown id). The singular 'One location by id' is the only implied routing signal.

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