os_tiles_ota_collections

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so the safety profile is covered. The description adds no behavioral context beyond the obvious listing action—it doesn't mention pagination, filtering, or return format. With annotations covering the essential traits, a 3 is appropriate.

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, clear sentence with no wasted words. It states the action and resource immediately, which is ideal for a listing tool.

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?

The tool is simple (no required parameters, output schema exists), so the description is functionally sufficient. However, given the large sibling set of OS OTA tools, a brief note on what 'tile collections' are or how this differs from conformance/tilematrixsets would improve completeness. It doesn't fail to provide critical info for a straightforward list operation.

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 parameter is a constant string ('tool'), so the schema fully defines it. The description adds no parameter details, but none are needed for a constant. Schema coverage is 0% because the description doesn't reference parameters, but the triviality of the parameter keeps this at 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 uses a specific verb ('List') and a specific resource ('OS NGD OTA tile collections'). It clearly indicates the tool enumerates tile collections. While it doesn't explicitly differentiate from sibling tools like os_tiles_ota_conformance or os_tiles_ota_tilematrixsets, the resource name is distinct enough to infer the purpose.

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 description gives no guidance on when to use this tool versus alternatives. Sibling tools like os_tiles_ota_conformance or os_tiles_ota_tilematrixsets exist, but the description doesn't explain which scenario calls for listing collections versus checking conformance or tilematrixsets.

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