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

Annotations already declare read-only/idempotent/non-destructive, so the lower bar applies. The description adds real value beyond them: it discloses the return shape (topic numbers, titles, one-line summaries, UNVERIFIED counts) and documents the confidence-tag vocabulary ([V], [V-mfr], [UNVERIFIED], [inference], [Expert]). That tag legend is behavioral context an agent cannot get from structured fields.

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 verb and primary guidance are front-loaded, and the confidence-tag sentence earns its place. The 18-item parenthetical coverage list is long and partially restates content the tool itself returns as topic titles, so it is slightly heavier than necessary.

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 zero-required-parameter listing tool with an output schema, the description is complete enough to invoke correctly and to interpret the confidence tags. It redundantly describes return fields the output schema already covers and never mentions the one optional parameter, keeping it from a 5.

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 100% and the single parameter include_sections is fully documented in the schema, so the description is not obliged to add parameter detail. It mentions section-level output only indirectly ('include_sections' is never referenced), so baseline 3 is correct.

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 (List) plus the resource and its exact size, and enumerates the subject coverage so an agent can tell it apart from search_glazing_knowledge and get_topic without opening a schema.

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?

'Call this first if you are unsure which topic covers a question' gives a clear trigger condition and implicitly routes to get_topic once a topic number is known. It does not explicitly state when not to use it (e.g. when the topic is already known), so it falls short of a 5.

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