data_freshness

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

The annotations already declare readOnlyHint=true and destructiveHint=false. The description adds transparency by specifying a 5-minute cache, minimal cost (1 SELECT), and listing exactly which data sources are covered and excluded. There is no contradiction with annotations.

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 well-structured with paragraphs covering output, usage, exclusions, and caching. It is front-loaded with key fields and purpose. While detailed, it earns its length; however, minor redundancy (e.g., repeating alert thresholds) could be trimmed, preventing a perfect 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?

Given the tool's complexity, the description covers all necessary aspects: returned fields, alert thresholds, exclusion of live sources, cache behavior, and cost. The presence of an output schema further reduces the need to explain return values, so the description is contextually complete.

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 tool has zero parameters and the input schema has 100% coverage. According to rules, baseline is 4 for no parameters. The description implicitly indicates no input is needed by listing no parameters, but it doesn't add further meaning beyond what the schema already provides.

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 returns the freshness of data dumps for specific sources (FINESS, Ameli, RPPS, Centres de Santé) and lists the returned fields. It distinguishes itself from sibling tools that deal with specific entities or live data, making the purpose unambiguous.

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 explicitly says to use this tool before territorial audits or temporal analysis. It provides alert thresholds for each source and clarifies that live sources are not included. It also mentions caching and cost, giving explicit guidance on when and how to use the tool.

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