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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so the safety profile is fully covered. The description adds only the organization-wide scope; it says nothing about ordering, pagination beyond the limit param, or empty-result behavior.

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 sentences, front-loaded with the action and resource. Nothing is wasted, though the second sentence is a fragment that could be folded into the first.

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?

A simple list tool with an output schema, full parameter documentation and comprehensive annotations needs little prose. The only meaningful gap is the lack of guidance on how the returned sites are used downstream by site-scoped siblings.

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?

There is a single parameter with 100% schema description coverage ('Max sites to return (1-100, default 50)'), so the schema carries the full burden. The description adds no further meaning about the limit.

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 and resource ('List all sites (tenants) in your organization') and disambiguates the term sites as tenants. It reads clearly against siblings like list_clusters and list_articles, though it does not explicitly distinguish itself from them.

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 phrase 'For agency accounts managing multiple sites' implies the intended audience but gives no explicit when-to-use/when-not guidance or alternatives. An agent must infer that this is the entry point for discovering the sites it can then pass to site-scoped tools.

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