get_today_events

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

With no annotations provided, the description carries full burden but discloses minimal behavioral traits. It mentions retrieving events but doesn't describe authentication requirements, rate limits, pagination behavior, error conditions, or what happens with invalid calendar IDs. The description doesn't contradict annotations (none exist), but provides inadequate behavioral context.

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 appropriately brief with two sentences and an Args section. The front-loaded purpose statement is clear, though the Args formatting could be more integrated. No wasted words, though slightly more context could improve completeness without sacrificing conciseness.

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 read operation with no annotations, no output schema, and minimal parameter documentation, the description is insufficient. It doesn't explain what format events are returned in, whether results are filtered by time of day, authentication requirements, or how it differs from sibling tools. The description leaves too many contextual gaps for effective tool selection.

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?

The description adds the parameter 'calendar_id' with a brief explanation and default value, but with 0% schema description coverage and only 1 parameter, this provides basic compensation. However, it doesn't explain what constitutes a valid calendar ID format, whether 'primary' is a special value, or what happens with invalid IDs.

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 'Get today's events from the primary calendar' which specifies the verb (get), resource (events), and temporal scope (today). However, it doesn't explicitly differentiate from siblings like get_calendar_events or get_upcoming_events, which likely have different filtering capabilities.

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?

The description provides no guidance on when to use this tool versus alternatives like get_calendar_events or get_upcoming_events. It mentions 'primary calendar' but doesn't explain when to use this versus other calendar tools or what makes 'today' different from other time ranges.

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