local_risk_france_search_data_gouv

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

With no annotations provided, the description should disclose behavioral details such as read-only nature, pagination, rate limits, or output format. It simply states 'search' with no additional context, adding nothing beyond the tool name itself, which is nearly a tautology.

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, concise sentence that is front-loaded and free of fluff. It earns its place by conveying the core action, though it could be more informative without sacrificing brevity.

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?

This is a simple tool with only two parameters and no output schema, but the description fails to explain what the response will look like or any constraints on usage. Without annotations or output schema, it is insufficiently complete for an agent to fully anticipate outcomes or limitations.

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 100%, so the parameters 'query' and 'page_size' are already documented. The description adds no extra semantic value beyond the schema, which meets the baseline but does not enhance the agent's understanding of parameter nuances.

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 public datasets on data.gouv.fr using the official API, with a specific verb and resource. However, it does not distinguish itself from sibling tools like 'local_risk_france_search_risk_datasets', which likely serves a similar purpose, so it misses the mark for full 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. The description merely states what it does without any context on preferred scenarios, prerequisites, or tools to avoid, leaving the agent to infer usage.

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