transport_search_datasets

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, making behavior clear. The description adds concrete return structure (name, description, formats, download URLs) and catalog size (~90 datasets), enriching understanding 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?

The description is very concise: three sentences front-loading the purpose (search catalog), listing content categories, and specifying return fields. No unnecessary words, every sentence adds value.

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 annotations (readOnly, idempotent) and existence of an output schema, the description provides adequate context: catalog scope, example dataset types, and return structure. It could mention pagination or result count, but it's sufficient for a straightforward search tool.

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 already describes both parameters (query required, limit optional with constraints). The description adds value by providing concrete search term examples ('gtfs', 'fahrplan', 'realtime') and clarifying that results are datasets from opentransportdata.swiss, which aids parameter interpretation.

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 clearly states the tool searches the Swiss transport open data catalog (~90 datasets), enumerating example dataset types (timetables, GTFS, etc.) and return fields. It distinguishes from sibling tools like transport_search_stop or transport_departures by focusing on dataset metadata.

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 for finding transport datasets and gives search examples ('gtfs', 'fahrplan'), providing clear context. However, it does not explicitly state when to use this vs. alternatives like transport_search_stop or transport_get_dataset, though sibling differentiation is achievable from context.

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