Propose New Meeting Time

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

Annotations indicate write operation and side effects (openWorldHint=true). The description adds 'requires user confirmation recommended' but doesn't detail the process or potential side effects adequately.

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 well-structured with a summary, usage note, and parameter list. It's slightly lengthy but not wasteful. The 'requires user confirmation recommended' could be phrased more concisely.

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?

The description covers basic usage, but given openWorldHint=true and an output schema exists, more details about what happens after proposing (e.g., organizer receives request) would improve completeness.

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?

Despite 0% schema coverage, the description includes detailed Args with examples (ISO date formats) and explains each parameter's purpose, fully compensating for the schema's lack of descriptions.

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 proposes a new meeting time, specifying it's for attendees only, which distinguishes it from sibling tools like calendar_update_event for organizers.

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?

It explicitly says when to use: when invited but the time doesn't work, and notes the limitation of only working for attendees. It doesn't name alternatives but provides clear context.

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