calendar_get_unconfirmed_events

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

The description indicates it's a read operation, but with no annotations, it does not disclose authentication needs, pagination behavior, or output format, which is minimal but adequate for a simple tool.

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 a single concise sentence, but it is only in Chinese; an English translation would improve accessibility for multilingual agents.

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?

Without an output schema or parameter details, the description fails to explain return values or pagination, leaving the agent underinformed for a simple listing tool.

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 two parameters (page_size, page_index) are not explained in the description, and schema coverage is 0%, so the agent must infer their purpose from names alone.

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 gets unconfirmed event invitations for the current user, using a specific verb and resource, and distinguishes it from sibling calendar tools like calendar_get_events.

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?

No guidance is provided on when to use this tool versus alternatives, such as when to use calendar_get_events for confirmed events.

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