list_today

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

No annotations are provided, so the description carries the burden. It does add one useful behavioral detail, the calendar's local timezone semantics for 'today', but says nothing about permissions, result limits, or ordering. An output schema exists, so return shape is covered elsewhere.

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?

A single, front-loaded sentence with the scope qualifier in parentheses; no wasted text. It is appropriately terse for a simple list tool.

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?

With an output schema present and low complexity (one optional boolean), the description is close to adequate, but the undocumented parameter and absence of any usage framing leave meaningful gaps for an agent choosing among calendar siblings.

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?

There is one parameter (include_description) with 0% schema description coverage and a default of false, and the description never mentions it. With coverage below 50% the description should compensate, but it adds no meaning about what this flag does or when to set it.

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 (List) plus resource (events) and a clear temporal scope (occurring today), which differentiates it from list_events and list_upcoming. It does not explicitly name those siblings, so the differentiation relies on the reader noticing the 'today' scope.

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 'today' scope implies when to reach for this tool, but there is no explicit when-to-use/when-not guidance and no reference to the alternatives (list_events, list_upcoming, search_events). Usage is only inferable from the name and scope.

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