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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds nothing behavioral beyond that — no pagination, filtering, or result-size context, and its single added sentence just defers to another tool.

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?

Short, but the first sentence is duplicated word-for-word, wasting half the text. What remains is an operation ID and a redirect, not front-loaded usefulness.

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 tool with a nested, undocumented query object and no output schema, the description gives an agent nothing about accepted query shape or return contents. The describe_operation pointer is the only lifeline, so an agent cannot call this correctly from the definition alone.

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 description coverage is 0% and the schema itself is a bare query/params object with additionalProperties, so the description had to compensate and does not. It mentions no parameter names, formats, or supported filters; the only help is a delegation to describe_operation, which is indirect rather than explanatory.

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?

It does name a concrete HTTP verb and resource (GET /api/inventory/locations), so the resource is identifiable and distinguishable from get_inventory_locations_by_id. But that is raw endpoint notation with no plain-language statement of what a 'location' record contains or why an agent would list them; the sentence is repeated verbatim rather than elaborated.

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?

No when-to-use guidance, no exclusions, no comparison to siblings such as get_sitefolio_locations or get_inventory_locations_by_id. The only actionable text is a pointer to describe_operation, which is a schema-discovery redirect rather than a usage rule.

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