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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false, destructiveHint=false), so the baseline is 3, and the description clears it by adding real context: each row's field inventory, the distribution roll-up, and the completeness guarantee that even guides with no rendering surface are included. This surfaces an audit-oriented behavior that 'list' alone would not convey.

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?

A single front-loaded sentence states verb, resource, and output scope before enumerating the row fields and roll-up; the parenthetical about unrouted guides earns its place by clarifying inclusion semantics. There is no filler, and the length is proportionate to the information conveyed.

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?

With a 100%-documented 13-parameter schema, an output schema, and rich read-only annotations, the description only needs to fill behavioral gaps, which it does well via the field inventory and roll-up note. The remaining gaps are minor — no statement of ordering, pagination beyond the limit cap, or whether filters affect the roll-up — so it falls just short of fully complete.

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 every one of the 13 parameters already carries a rich, example-laden description (domain explained as the layer above the subject shelf, format documented with row shapes and a server default, category noting primary OR cross-shelf tag matching), so the schema does the heavy lifting. The description lists output fields that map to some filters but adds no parameter-level detail on top of the schema, matching the baseline 3.

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 names a specific verb and resource — 'List the bicycle.guide registry' — and enumerates exactly what each row contains (home, status, access, standard, syndication, grounding) plus the distribution roll-up, so an agent knows precisely what it returns. It does not explicitly contrast a sibling (e.g., that get_guide fetches a single guide), so differentiation from siblings is implicit rather than stated.

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?

The registry framing and 11 optional filters imply this is the browse/audit-all entry point, and the 'including guides homed to a property with no rendering surface' clause hints at a distribution-gap audit use case. However, there is no explicit 'use this when X, use get_guide/list_capabilities/list_taxonomy when Y' guidance, so when-to-use must be inferred.

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