os_features_wfs_capabilities

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

The annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds the context that this is a WFS GetCapabilities fetch, which is consistent with those annotations, but it discloses no additional behavioral details such as response format, potential size limits, or interaction with delivery/inlineMaxBytes. This is adequate but not enriching.

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 sentence with no filler; it is front-loaded with the action and resource. It is concise, though arguably too sparse to serve as the sole source of guidance for a tool with four parameters and a close sibling. Still, it earns its place and avoids redundancy.

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 relatively simple, has no required parameters, includes a safe read-only/idempotent annotation set, and has an output schema, so the description does not need to explain return values. However, it omits any explanation of optional parameter semantics and does not clarify how this differs from the archive capabilities sibling. It is minimally viable but not complete enough for confident non-default usage.

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 0%, so the description should compensate for the four parameters, but it mentions none of them. The parameters version, delivery, and inlineMaxBytes have no explanatory text in the description; even the meaning of the delivery enum (inline/resource/auto) is left entirely to the agent. The description adds no semantic value beyond what the schema already shows.

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 ('Fetch'), a specific protocol operation ('WFS GetCapabilities'), and a specific resource ('OS Features API'). This is clear and unambiguous at a high level. However, it does not explicitly distinguish itself from the sibling tool os_features_wfs_archive_capabilities, so it stops short of full sibling differentiation.

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 guidance on when to use this tool versus alternatives such as os_features_wfs_archive_capabilities, os_features_collections, or os_features_query. No conditions, prerequisites, or exclusions are stated, leaving the agent to infer usage entirely from the tool name and the single-line description.

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