data_gouv_fr_list_dataset_resources

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

With no annotations provided, the description carries the burden of behavioral disclosure. It notes the optional format filter and that the output provides direct URLs, but does not mention pagination behavior, authentication requirements, or potential empty results. This is acceptable but not rich in detail.

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 compact and front-loaded with the core purpose ('List resources/files'), followed by the optional filter and usage guidance. Every sentence contributes useful information without redundancy.

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 low-complexity tool with a complete schema, the description is sufficient. It explains the tool's role in the workflow, the nature of the output (URLs), and the optional filter. It could add more about the exact return structure, but is not incomplete given the simple scope.

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 parameters are already well-documented. The description adds minimal value by highlighting the optional format filter, but does not go beyond the schema's own descriptions for 'dataset', 'limit', or 'format'.

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 that the tool lists resources/files for a data.gouv.fr dataset with an optional format filter. This distinguishes it from sibling tools like data_gouv_fr_get_dataset, and the 'use after' instruction reinforces its specific role.

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 usage context: 'Use after data_gouv_fr_get_dataset when the agent needs direct CSV/API/file URLs.' This tells when to invoke the tool, but does not explicitly mention when not to use it or name alternative tools for other resource-related needs.

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