os_features_collections

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds a small behavioral detail—the 'latest-by-base mapping'—but does not explain what that mapping means or any pagination/filtering behavior beyond what annotations imply.

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 a single front-loaded sentence with no filler. It states the core action first and adds the mapping nuance parenthetically without wasting words.

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 simple read-only listing tool with an output schema and safety annotations, the description is mostly adequate. However, the phrase 'latest-by-base mapping' is unexplained jargon, and there is no usage guidance relative to closely related feature/tile collection tools, leaving a moderate gap.

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 only meaningful parameter, q, is already described in the schema as 'Optional substring filter.' The description adds no additional parameter context, but with just one real parameter and a self-describing const, the schema carries the necessary semantics. 50% schema coverage is partially compensated by the trivial nature of the parameters.

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 a precise resource ('OS NGD OGC API Features collections'), plus a distinct 'latest-by-base mapping' nuance. It is clearly distinct from query-oriented siblings like os_features_query, though it does not explicitly name alternatives.

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?

No guidance is given about when to use this tool versus sibling tools such as os_features_query, os_features_wfs_capabilities, or os_tiles_ota_collections. The agent must infer the appropriate context from the name and description alone.

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