cancel_meeting

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

Without annotations, the description only mentions return of confirmation message. No disclosure of side effects, cancellation policies, or impact on other systems. Additionally, the description claims topic is optional while schema requires it, creating confusion.

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?

Short but uses unnecessary docstring formatting ('param', 'return'). Adequately concise but could be cleaner.

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?

Given no annotations, the description is incomplete. It omits prerequisites (meeting existence), cancellation consequences, and the contradiction on topic weakens reliability.

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?

With 0% schema coverage, the description adds minimal value: employee_id is trivial, meeting_datetime gives format but no constraints, topic is incorrectly marked optional. No explanation of how these parameters identify a meeting.

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?

Clearly states 'Cancel a scheduled meeting' with specific verb and resource. Distinguishes from siblings like schedule_meeting (opposite) and get_meetings (different action).

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 explicit when-to-use or alternatives given; the cancel action is implied but lacks context like prerequisites or when not to use (e.g., meeting already passed).

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