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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world scope, so safety is covered. The description adds nothing beyond that — no note on pagination, filtering behavior, or the fact that the 'query' object accepts arbitrary keys.

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?

It is short, but the first two sentences are verbatim duplicates of the same path string, so the length is wasted rather than efficient. The only substantive content, the operation ID and the describe_operation pointer, sits behind redundancy.

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?

With no output schema, zero parameter documentation, and a nested free-form 'query' object, the description should explain the request shape and return payload. It does neither, leaving the agent to fall back on describe_operation for basic invocation.

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% for two parameters, and the description compensates with nothing. An agent cannot learn from the text that 'query' is a free-form additionalProperties object while 'params' is an empty closed object — a distinction that materially affects how to call the tool.

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 only repeats the HTTP path 'GET /api/sites' twice, which restates the name and title without saying what a site is or what the call returns. There is no differentiation from siblings such as find_sites, get_sites_by_id, or the sitefolio location tools.

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 only directive is that 'describe_operation provides native request schemas', which is a schema-discovery hint rather than guidance on when to call this versus find_sites or the more specific get_sites_by_id_* tools. No conditions, prerequisites, or exclusions are given.

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