send_meeting_invitation

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

No annotations are provided, so the description carries the full burden: it discloses a deliberate send gate (default false means nothing is sent), idempotency-style protection against duplicate invites, and a hard cross-tool prerequisite on calendar_ref. It omits what happens after a successful send (recall/cancellation) and any permission requirements, which matters for an unannotated, irreversible-looking mutation.

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?

Three short lines, front-loaded with the action and the gating condition, followed by rejection behavior and the prerequisite. No sentence is redundant with the name or schema.

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?

An output schema exists, so return values need not be explained, and the description covers the mutation's precondition and failure states. For a write tool with zero annotations, a note on permissions or post-send irreversibility would close the remaining gap.

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%, so the description must compensate, and it does for both parameters: confirm_send is given real gating semantics (explicit true required, default false is a no-op) and calendar_ref is given provenance (must come from save_meeting/read_calendar). Only the expected format/identity of calendar_ref is left unstated.

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+resource (send a saved, not-yet-sent meeting invitation) and immediately distinguishes itself from save_meeting and read_calendar, which it names as the sources of calendar_ref. An agent can tell this apart from its siblings without opening a schema.

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?

Explicitly names the precondition (confirm_send=true must be set explicitly), the states that cause rejection (already-sent or cancelled meetings, to avoid duplicate invitations), and the alternative tools that supply the required reference. This is effectively when-to-use, when-not-to-use and alternatives in three lines.

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