Daily Report (Cross-Channel)

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

No annotations provided, so description carries full burden. It discloses the fixed 7-section structure, return type (SynthesisResult with sections, answer, citations, gaps), and error behavior (valid ISO date required). No contradictions with missing 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?

Concise, well-structured with explicit sections (title, description, when to use/not, returns, error). Every sentence adds essential information without redundancy. Front-loaded with core purpose.

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 simple one-parameter tool with no output schema, the description fully covers purpose, usage, return structure, and error handling. No gaps given the tool's complexity.

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 coverage is 100% for the single parameter 'date', but description adds value by specifying format (YYYY-MM-DD), default (today local time), and error condition. Baseline 3 plus extra context yields 4.

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 states 'Generate a synthesized cross-channel daily report in 7 fixed sections' – a clear verb+resource+scope. It explicitly distinguishes from siblings by naming 'recall' and 'query' as alternatives for arbitrary recall, making purpose unmistakable.

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?

Explicit when-to-use ('help me write today's daily report') with a list of aggregated signals, and a clear when-NOT-to-use ('arbitrary recall; use recall/query'). Provides context for tool selection.

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