icu_get_activities_by_date

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

Annotations already indicate read-only, open-world, idempotent, and non-destructive. The description adds that results are newest-first, oldest dropped if limit exceeded, and that it returns a 'light summary.' These add context beyond annotations, but could further clarify what 'light summary' entails.

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 extremely concise, using only a few sentences. It front-loads the core purpose, contrasts with a sibling, and uses bullet-like dashes for clarity. Every sentence serves a purpose with no fluff.

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 (4 params, output schema exists, rich annotations), the description is complete. It explains date window, ordering, limit behavior, and offers usage guidance. The output schema likely covers the return structure, so no further detail needed.

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 for all 4 parameters. The description reinforces date format (YYYY-MM-DD), defaults, and the limit's impact on dropping oldest items. It adds value by explaining behavior, but the schema already covers basic parameter meanings.

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 activities within an explicit date window with a light summary. It specifies the verb 'list' and resource 'activities,' and immediately contrasts with the sibling icu_get_recent_activities, making its purpose distinct.

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 provides when to use this tool vs. the sibling, including concrete use cases like 'all my runs from June to November 2025' and advice on handling the limit parameter. It also explains ordering and dropping behavior for oldest items.

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