calendar_add_members

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

No annotations provided; the description only states the action (add members). It does not disclose side effects (e.g., notifications), permissions, or behavior for recurring events. The recurring-event parameters are mentioned in schema but not explained.

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?

Two short sentences with no wasted words. Purpose first, followed by parameter details. Highly concise and well-structured.

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?

Lacks completeness for an agent to use correctly. Does not explain required field (event_id), recurring event handling, or return output. For a 5-parameter tool with no output schema, the description is too sparse.

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?

Schema description coverage is 0%. The description adds meaning for member_ids and invited_accounts (format and user types), but fails to explain event_id (required), event_recurring_time, and modifying_all_recurring_events. Covers 2 of 5 parameters.

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 it adds members to a schedule/event. It distinguishes between internal (member_ids) and external (invited_accounts) members, but does not explicitly differentiate from sibling tools like calendar_edit_event.

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?

Provides format guidelines for member_ids (comma-separated) and invited_accounts (array format ['phone','email']). Implies when to use each parameter, but does not state when not to use the tool or suggest alternatives.

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