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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds useful conceptual context about partials and render locations, but says nothing about pagination, auth, or the shape of results beyond render locations.

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?

The description is a single front-loaded fragment with no wasted words. It is efficient for a simple list tool, though its terseness contributes to the missing action verb and usage context.

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 simple read-only list tool with rich annotations and a simple schema, the description is minimally adequate. However, with no output schema, it could do more to explain what the returned 'where each renders' data looks like and whether a site id is needed to scope results.

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?

The single 'id' parameter is fully described in the schema as 'Site id.', so schema coverage is 100%. The description adds no parameter-specific meaning, which is acceptable under high schema coverage but not above baseline.

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 identifies the resource as reusable components (partials) and adds that it shows where each renders, which goes beyond the name. However, it never states the verb 'list' and reads as a fragment, leaving the action implied rather than explicit.

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 guidance on when to use this versus list_pages, list_site_files, or other list tools, and no prerequisites or site-context requirements are mentioned. The 'HTML-first sites' phrase hints at a domain constraint but does not route the agent to alternatives.

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