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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds no behavioral context of its own: no note on response shape, pagination, or whether the catalogue is static or reflects live configuration.

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 with no filler, listing the two things returned (checks and sources). It is appropriately sized for a simple listing tool; only the minor redundancy between 'sources behind them' and the road_legal_data_sources sibling keeps it short of ideal.

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 no output schema, the description should carry more of the return-value burden, and 'checks' and 'sources' is only a rough sketch of the payload. For a one-parameter, read-only discovery tool this is minimally adequate, but an agent cannot tell what a catalogue entry looks like or how to page through it.

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?

There is a single optional 'query' object parameter whose schema already carries a description ('Optional query parameters'), so schema coverage is 100% and the baseline is 3. The description adds nothing about what the query object can filter on, which matters because the schema only declares arbitrary string/number/boolean properties.

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 ('List') and a specific resource ('the checks Road Legal Pass performs and the sources behind them'), so an agent knows this is discovery/introspection rather than an actual check. It partially distinguishes from siblings like road_legal_check, but the phrase 'the sources behind them' overlaps with road_legal_data_sources, leaving some ambiguity about which to call for source metadata.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. The sibling set contains road_legal_check and road_legal_data_sources, which are obvious candidates for a routing sentence, but the description never mentions them or says when the catalogue is preferable.

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