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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully carried by structured data. The description adds only the HTTP method/path and the fact that a short name is the public-URL segment; it says nothing about return shape, errors, or rate limits.

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?

One sentence plus the endpoint, front-loaded with the resource and accepted identifier forms. No filler, no restatement of the title.

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 trivial single-resource fetch with annotations covering safety and a 100%-documented schema, this is nearly complete. The only gap is that no output schema exists and the description does not hint at what a location object contains or how an invalid identifier is reported.

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% and the single parameter is documented there, so baseline is 3. The description earns an extra point by defining what a 'short name' actually is ('the part of its public Waitwhile URL'), a clarification the schema does not provide.

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 (get) and resource (one location), plus the exact endpoint GET /locations/{shortNameOrId}. It implicitly contrasts with list_locations and get_location_status by scoping to 'one location by id or short name', though it never names those siblings explicitly.

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 rather than stated: an agent can infer this is for retrieving a single known location. There is no explicit when-to-use, no guidance on choosing this over waitwhile_list_locations or waitwhile_get_location_status, and no mention of failure behavior for an unknown id.

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