Search datasets

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

Discloses API behavior (AND logic, zero results for generic words) and explains sort and range options. Annotations already declare readOnly and idempotent, so description adds value without contradiction.

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?

Concise, front-loaded with purpose, no redundant sentences. Well-structured with usage tips and workflow hint.

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?

Covers purpose, key parameters, and typical workflow. Output schema exists so return values need not be detailed. Slightly more guidance on page_size default would help.

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 has 0% description coverage. Description adds meaning for sort and last_update_range, but query, page, and page_size lack elaboration beyond schema basics. Acceptable given query is self-explanatory.

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?

Clearly states the tool searches for datasets on data.gouv.fr by keywords. Differentiates from siblings by being the first step and listing a typical workflow.

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?

Provides explicit guidance on query format (short, specific, AND logic) and sort/last_update_range parameters. Mentions typical workflow but does not explicitly exclude alternatives.

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