data_freshness

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

Discloses cache duration (5 minutes) and cost (1 SELECT). Annotations indicate readOnlyHint=true, which aligns with description. No contradictions.

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?

Description is front-loaded with purpose and structured into logical sections: sources, fields, usage, alerts, exclusions. Each sentence adds 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?

Comprehensive coverage of all aspects: returns, usage, cache, cost, live source exclusion. Output schema exists, so description doesn't need to detail every field, but it sufficiently explains the tool's role.

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?

Input schema has no parameters, so description adds value by confirming no input needed and detailing output fields. Baseline 4 is appropriate.

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?

Description clearly states the tool returns freshness of specific data dumps (FINESS DREES, etc.) with fields and cadences. Distinguishes from sibling tools by focusing on data freshness meta-information.

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 scenario (before territorial audit or temporal analysis) and specific alert thresholds for each source (e.g., staleness_days > 90 for FINESS). Also clarifies that live sources are excluded.

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