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

Annotations already declare idempotentHint and destructiveHint, so the description's idempotency note is partly redundant. However, it adds behavioral context annotations do not carry: the authorization model (go-ahead IS the send authorization, no separate confirmation), the governance-policy approval path, and specific error conditions (meeting not awaiting the invitee's pick; shareable mode with no invitee email, use picker_url instead).

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 first paragraph front-loads the key behavior well, but the "When to use" paragraph restates much of it (same-turn rule, hold-the-send condition, never on own initiative, idempotency), creating redundancy rather than added value. The example is useful, but the repetition dilutes structure.

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?

With an output schema present (returns the meeting's full state) and rich annotations, the description is nearly complete. It covers authorization, idempotency, error paths, and the governance caveat. Minor gap: no explicit statement of required permissions beyond the governance note, but this is adequately covered for the tool's complexity.

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 100% with a single meeting_id parameter whose format and pattern are fully documented, so the schema does the heavy lifting. The description adds no syntax or format detail beyond naming the source (propose_meeting or search_records) indirectly. Baseline 3 is appropriate.

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 and resource ("Sends the picker email to the invitee") and implicitly distinguishes itself from propose_meeting, which is named as the prerequisite step. An agent can identify this as the send/finalize action in the meeting flow without opening the 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?

Explicit when-to-use rules: call in the SAME turn as propose_meeting after the user okays topic+agenda, call standalone only when the user earlier said to hold the send. It also states hard exclusions (never without a clear human go, never on the model's own initiative).

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