collection_calendar

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

No annotations provided, so description carries full burden. It describes return fields (date, label, daysUntil, fractions) but does not disclose error handling, required permissions, or behavior on invalid addresses. Lacks details on side effects or rate limits, though tool is read-only.

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?

Two well-structured sentences: first states core function and return format, second gives usage guidance, third details parameters. No fluff, each sentence adds value.

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?

Covers purpose, usage, parameters, and return format (important since no output schema). Missing details on authentication, error handling, or scope limitations beyond 'Horsens address'. Adequate for a simple read tool.

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% with descriptions identical to the description. The description restates parameter meanings (address type, weeks range) without adding new semantic value beyond the schema, so baseline of 3 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?

The description clearly states the tool returns upcoming waste collection events for a Horsens address over N weeks, using specific verb 'return' and resource 'waste collection events'. It distinguishes from siblings find_address (address lookup) and next_collection (single next event) by emphasizing multi-week look-ahead.

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?

Explicitly states when to use: 'Use this when ARIA needs to plan ahead or answer "hvornår tømmes X de næste uger?"' This directly guides the agent to choose this tool for planning multiple weeks rather than a single next collection.

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