Discover REST routes

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with them (a list operation). Beyond annotations, it adds that results reflect live site registration including plugin additions, and that route shapes vary between plugin versions — useful open-world context consistent with openWorldHint=true. No contradiction with 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?

Two sentences, both earning their place: the first states the core function, the second delivers usage guidance with a rationale. Information is front-loaded with purpose before context, with no filler or repetition of schema/annotation content.

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 discovery tool, the description covers purpose, when to use it, and the basic return content (namespaces and routes). Annotations cover the safety profile and open-world nature, and the schema documents all parameters. The minimal return description suffices for the stated use case of feeding rest_api.

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%, with all three parameters (search, site_id, namespace) already documented in the schema. The description adds no parameter-specific semantics beyond what the schema provides, so the baseline 3 applies.

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 states a specific verb + resource: it lists the REST namespaces and routes the site actually registers, including plugin-added ones. It distinguishes itself from siblings like rest_api by scoping to actually-registered routes rather than theoretical ones, making its purpose unambiguous.

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?

Explicit guidance is provided: 'Use this before rest_api so you call routes that exist' — naming the alternative tool directly and giving the condition plus rationale (route shapes vary between plugin versions, guessing wastes calls). There is no ambiguity about when to invoke this tool.

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