Icu Get Calendar Events

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing that results are unfiltered and enumerating the entry types returned, which tells the agent what to expect in the payload. It stops short of noting size/pagination behavior for wide date windows.

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?

Three short lines: scope statement first, use cases second, sibling routing last. Every sentence carries information an agent needs; there is no repetition of the title or schema.

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?

Output schema exists so return values needn't be explained, annotations cover safety, and the schema covers all three parameters. The only residual gap is a trivial one: the sibling is referenced as "get_event" rather than its full name icu_get_event, which could momentarily confuse routing.

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 description coverage is 100%, so days_back, days_ahead and athlete_id are fully documented in structured form and the baseline applies. The description alludes to a "date window" but adds no syntax, defaults or edge-case guidance beyond the schema.

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?

States a specific verb (fetch) and resource (calendar entries) plus the scope (a date window, ALL entry types enumerated: workouts, notes, races, goals, life-event blocks). It explicitly marks itself as the unfiltered/broad variant, which separates it from icu_get_upcoming_workouts and icu_get_event.

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?

Gives concrete trigger queries ("what's on my calendar?", "show this week", broad calendar queries) and names both alternatives with the condition that selects each — filtered workout-only lookups go to icu_get_upcoming_workouts, single-event lookups go to get_event. Nothing is left to inference.

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