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

With readOnlyHint=true already provided, the description adds meaningful context: it is an orientation-only tool, not a content search, and it enumerates the categories. It does not detail the exact return shape, but the presence of an output schema mitigates that gap.

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 front-loaded with a one-line purpose, then gives a tight usage rule, an exclusion, and a clear category list. Every sentence adds value, and the structure is scannable without being bloated.

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 tool's simple input (one optional param), read-only annotation, and existing output schema, the description covers purpose, when/how to use, category options, and relation to sibling tools. Nothing important is missing for a tool of this complexity.

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 schema has one optional param with an enum but zero description coverage; the description fully compensates by listing and explaining the category values (natives, vorp, rsgcore, etc.) and connecting them to content areas. This goes well beyond raw enum labels.

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 uses a specific verb ('list') and resource ('available doc categories and their namespaces'), clearly distinguishing itself from content-search tools by stating 'NOT a content search' and naming related tools like 'browse' / 'semantic_search'. This makes the tool's role unmistakable.

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?

It explicitly states when to use the tool ('Use once at session start (or when unsure)') and frames it as a prerequisite before applying category or namespace filters to other tools. It also gives an exclusion ('NOT a content search'), which is strong usage guidance.

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