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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and a closed world, so the safety profile is fully covered. The description adds that the listing is exhaustive ('every document this server can read') and that summaries are included, but it does not disclose ordering, size limits, or what happens if no documents exist. With annotations carrying the behavioral load, this is adequate but thin.

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 with zero filler; the exhaustive-listing scope is front-loaded and the usage hint follows immediately. Nothing could be removed without losing routing information.

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 read-only, zero-required-parameter listing tool with an output schema and 100% schema coverage, the description covers purpose and routing adequately. Minor omissions such as ordering or behavior with an empty server are low-risk given the output schema defines the return shape.

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 parameter has full schema description coverage including its default and the effect of passing false, so the schema does the work. The description's mention of a 'one-line summary of each' echoes the default behavior of include_summaries but adds no syntax or override detail beyond the schema.

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 every document this server can read') plus the scope constraint that it returns the complete set with a one-line summary each. It also contrasts itself with search_docs by framing itself as the browse-everything option, so an agent can distinguish it from the sibling 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?

Gives explicit routing guidance: 'Call it first if you would rather choose a document than search across all of them,' which names the decision criterion against search_docs. It stops short of stating when the full listing is a bad idea (e.g., very large document sets or latency concerns), so no exclusion is present.

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