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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds nothing on top: no mention of pagination, filtering behavior, result size, or what the closed-world Sitefolio integration returns.

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?

Very short, but the one piece of content is duplicated verbatim ('GET /api/sitefolio/locations' twice) and the second sentence is an operation ID plus a cross-reference. Nothing is front-loaded as meaningful guidance, so brevity here reflects under-specification rather than efficiency.

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?

This is a list endpoint with a nested free-form query object, no output schema, and 0% schema description coverage — the description should be carrying substantial weight, but it carries none. An agent cannot tell what fields exist, how to filter, or what the response contains without making a second describe_operation call.

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 both parameters are undocumented: 'query' is an unconstrained free-form object and 'params' is an empty object. The description never mentions either, offering only a pointer to describe_operation, which is a redirect rather than semantics for the free-form query object an agent must construct.

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 is a verbatim restatement of the HTTP path already given in the title, plus an opaque operation ID. It never says what a 'sitefolio location' is or how this listing differs from the sibling get_sitefolio_locations_by_locationId, so the agent gets no resource-level meaning beyond the name itself.

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 when-to-use, when-not-to-use, or alternative-sibling guidance. The only forward reference is 'describe_operation provides native request schemas', which points at a schema source rather than explaining when this tool should be chosen over get_sitefolio_config, get_sitefolio_sync_history, or the by-locationId variant.

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