outremer_search_territory_datasets

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

The description indicates a read-only search operation, but it does not explicitly state that it is non-mutating or mention any side effects, permissions, or rate limits. The lack of annotations leaves some ambiguity about behavior, though the nature of a search suggests safety.

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, well-structured sentence that directly conveys the tool's purpose without unnecessary words. It is appropriately sized and easy to understand.

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 description provides enough context for the tool's intended use, including the data source and scope. It does not describe the return format or output, but that is acceptable given the absence of an output schema and the simplicity of the search task.

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 descriptions fully cover the parameters (territory, topic, page_size) with clear examples and constraints. The description adds no extra meaning or usage details beyond the schema, so it meets the baseline for high schema coverage.

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's function: searching data.gouv.fr for datasets related to a specific French overseas territory. It is concise and distinguishes the action from sibling tools like listing territories or getting sources.

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 the tool should be used when a dataset search for a particular territory is needed, but it does not explicitly specify when to prefer this over alternatives. It lacks explicit guidance on when not to use it.

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