swisstopo_search_geodata

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. Description adds that it searches a STAC catalog, returns only metadata/collections (not direct downloads), and lists data types queried. This adds useful context beyond annotations.

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?

Description is very concise, using XML-like tags to structure use cases and important notes. Every sentence provides distinct value without 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?

Given the presence of an output schema and comprehensive annotations, the description provides adequate context: purpose, use cases, and relation to sibling tool. Could mention pagination behavior, but current details are sufficient for most use cases.

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%, meaning the parameter descriptions in the schema are not counted as sufficient. The tool description does not mention the query or limit parameters beyond the schema's own descriptions, failing to compensate for coverage gap.

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?

Description states it searches a STAC catalog for downloadable geodata, with specific use cases listing Orthophotos, height models, 3D buildings, and historical maps. It distinguishes from sibling swisstopo_get_collection by noting download links are via that tool.

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?

Use cases and important notes provide clear context for when to use this tool (searching for specific geodata types) and link to swisstopo_get_collection for downloads. However, it does not explicitly differentiate from similar sibling swisstopo_search_layers.

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