os_tiles_ota_conformance

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 that this lists supported conformance classes, which is a metadata query. It doesn't add behavioral details like whether the list is static or dynamic, or whether it requires network access, but the annotations carry most of the burden.

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?

One sentence, front-loaded with the verb and resource. Every word earns its place. No fluff or repetition of schema details.

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 no-parameter metadata listing tool with a readOnlyHint and an output schema present, the description is nearly complete. It tells the agent exactly what will be returned (OGC conformance classes) and the scope (OS NGD OTA). The only minor gap is not describing the output format, but the output schema likely covers that.

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 schema has only one parameter ('tool') which is a const, and schema description coverage is 0%. However, with zero meaningful parameters (the const is just a routing identifier), the description doesn't need to explain parameter semantics. The tool takes no user input, so the description's job is minimal here. Baseline 4 for 0-param tools is appropriate.

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 ('List') and resource ('OGC conformance classes supported by OS NGD OTA'), which clearly identifies the tool's function. It doesn't explicitly differentiate from siblings, but the resource is specific enough that an agent can distinguish it from other OS tile tools like os_tiles_ota_collections and os_tiles_ota_tilematrixsets.

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 implies usage context: it lists conformance classes for OS NGD OTA, which is a metadata/discovery operation. It doesn't explicitly state when to use this tool versus alternatives, but the resource-specific naming and the fact that it's a list operation provide reasonable context. No exclusions or alternative tool mentions are given.

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