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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered without description help. The description adds that the listing is exhaustive ('every document') and that filters are optional, but says nothing about pagination, result volume, or auth needs — modest added value on top of rich annotations.

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?

Front-loads the core verb and resource, then layers filters and usage in a single tight paragraph with no filler sentences. The perspective enum list and the 'first four are plain language' clause duplicate what the schema fields already say, which is mild redundancy but does not bloat the text.

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?

Output schema exists, so the description is not obliged to describe return values, and it covers what remains: scope of the listing, optional filters, domain-specific filter semantics, and when to prefer this over searching. Nothing an agent needs to invoke it correctly is missing.

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 articles/guides-only constraints plus enum meanings are already documented per-field in the schema. The description largely restates the 'perspective' and 'level' values, adding interpretation ('match the reader') but little syntax or format detail the schema lacks. 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 ('Lists') plus resource ('every document') and immediately scopes it with the available filters. The final sentence implicitly distinguishes it from search_documents by positioning it as the browse-the-shape tool rather than the lookup tool, so an agent can route correctly.

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?

Gives explicit when-to-use guidance: 'before searching, or when a search returned nothing' — the second clause is a genuine fallback rule that names the sibling's failure mode. It also instructs how to pick filter values ('Match the perspective to the person asking'), which is actionable selection guidance rather than vague context.

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