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

Goes well beyond the annotations by disclosing the 10-minute freeze window, the required owner-session confirmation, the two specific scopes (scheduling:agent_write, scheduling:invite_send), and the negative side-effect boundary ('sends no invitation; grants no permission'). This is exactly the mutation/auth context an agent needs and annotations cannot carry.

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 dense sentences, front-loaded with what the tool does and then the permission/effect boundary. Every clause (ten minutes, owner-session confirmation, the two scopes, no invitation) carries distinct operational weight.

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?

The description does not state what the preview returns (e.g., a freeze identifier needed for the later send), which matters given there is no output schema. Otherwise, with a self-describing nested schema and annotations covering the safety profile, the definition is complete enough to invoke correctly.

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%, but the schema itself is richly constrained (oneOf over create/reschedule/cancel, required fields, formats). The description's only added parameter meaning is naming the three action variants; request_id and the per-variant fields are left entirely to the schema.

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 ('freeze exactly one create, reschedule or cancel proposal') and immediately distinguishes itself from the real write siblings (book_meeting, reschedule_booking, cancel_booking) by asserting 'Preview sends no invitation.' An agent can tell this is a dry-run proposal tool 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?

Implicitly routes the agent: preview first, and actual sending demands 'separate explicit authenticated owner-session confirmation plus scheduling:agent_write and scheduling:invite_send.' It does not explicitly name the sibling send tools to call afterward, so it stops just short of a full when/when-not statement.

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