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

With no annotations present, the description carries full behavioral burden and does disclose that this is a read operation returning every document's slug, title and summary. It does not mention result-set size, ordering, or any pagination/limits, which matters for an unfiltered 'every document' listing, but the essential read-only contract is conveyed.

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?

Three short sentences, front-loaded with what is read and what it returns, then the alternative, then the use condition. Every sentence carries distinct information with no repetition of the title or name.

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-parameter, annotation-free, output-schema-free listing tool, the description supplies the return fields, the read-only nature, and sibling routing — everything an agent needs to call it correctly. Nothing material is missing given the tool's simplicity.

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 tool takes zero parameters, so the baseline is 4; the description correctly implies nothing is configurable. No parameter confusion is introduced by the text.

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 ('Reads the Mangrove Knowledge Base package') and enumerates the exact fields returned (slug, title, summary). It also distinguishes itself from kb_search and kb_get_document by naming both siblings, so an agent can place it precisely in the KB tool triad.

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?

Explicitly routes the agent: keyword search goes to kb_search, and this tool is for browsing or for obtaining a slug before calling kb_get_document. Both the when-to-use and the alternative conditions are stated outright, leaving nothing to inference.

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