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. The description adds one behavioral detail beyond annotations, '[no key]', which signals no authentication key is required, but does not discuss rate limits or other operational context.

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 terse fragment and front-loads the list of returned content. The appended '[no key]' is compact but slightly cryptic, and the lack of a full sentence makes it less polished than an ideal definition.

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?

Given the low complexity (0 params), rich annotations, and an existing output schema, the description provides enough context about what the summary contains and that no key is needed. It omits explicit usage guidance, but for a simple read-only site summary this is a minor gap.

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 are no parameters: the input schema has an empty properties object and no required fields. Per the rubric, 0 params yields a baseline of 4, and the description correctly does not waste space explaining parameters.

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 lists concrete contents ('Mission, shelves, how to cite, and links to llms.txt, skill.md, and Connect') which makes it clear what site_summary returns, but it uses no verb to state the action. It implicitly distinguishes itself as the only site-level summary tool among siblings that focus on articles, verses, and words.

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 description gives no when-to-use guidance, no alternatives, and no prerequisites. An agent has to infer that this tool is for fetching general site metadata rather than specific content.

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