french_energy_open_data_search_odre_catalog

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

With no annotations, the description must disclose behavior, but it only says 'Search'—no mention of result format, pagination behavior, sorting, or that this is a read-only operation. The default limit and query are visible in the schema, but the description adds no behavioral context beyond the verb.

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 focused sentence with no filler or repetition. It is efficient but so minimal that it borders on under-specification, which prevents a higher score.

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?

For a tool with two parameters, no annotations, no output schema, and several siblings, the description is too sparse. It does not explain what kinds of queries work, what the returned data looks like, or how this search relates to the sibling tools, leaving an agent to guess at usage.

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%, so the description must compensate, but it does not mention the query or limit parameters or clarify how they affect the search. The parameter names are somewhat self-explanatory, but no additional meaning is provided to help an agent construct a good search.

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 states the action ('Search') and the resource ('the ODRE OpenDataSoft catalog'), which distinguishes it from searching a different catalog like search_data_gouv. However, it does not clarify what ODRE or the OpenDataSoft catalog contains, leaving some ambiguity about the domain and scope.

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?

No guidance on when to use this tool versus siblings such as get_sources, fetch_source_excerpt, or search_data_gouv. The description implies a search use case but does not state conditions, exclusions, or alternatives.

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