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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), and the description adds useful context beyond them: an explicit confirmation flag, an exact-version requirement, a durable idempotency key, and the side effect that acceptance may trigger a confirmation communication. The side-effect disclosure is the most valuable addition; it doesn't address permissions or failure modes.

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 with zero filler; the action, scope, and required safeguards are front-loaded before the side-effect note. Every clause carries distinct information.

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?

For a mutation tool with an output schema, the description covers the essential context: precondition (pending), safeguards (confirmation, version, idempotency), and side effects. It is nearly complete, missing only authorization/session expectations and behavior when the proposal is no longer pending.

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 description coverage across 6 parameters, the description must compensate, and it meaningfully documents action, responseConfirmed (explicit confirmation), expectedVersion (exact application version), and idempotencyKey (durable). It leaves sessionToken and proposalId unelaborated, though proposalId is at least implied by the tool's scope.

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 pair (accept/decline) and an exact resource (one pending Elron Club proposal), scoped to a single proposal. An agent can immediately distinguish this from viewings.get_status and viewings.propose_availability without opening any 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?

The word 'pending' and 'one ... proposal' give clear applicability conditions (single, still-pending proposal), and 'Acceptance may send the existing viewing confirmation communication' flags a consequential branch. It stops short of naming what to call instead for non-pending proposals or an explicit when-not to use.

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