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

The readOnlyHint=false annotation already signals mutation. The description adds important behavioral context beyond annotations: the tool is 'confirm-gated' and 'previews until confirm: true,' which tells the agent that calls are safe to preview but require an explicit confirmation step to execute. It does not describe side effects of accepting or declining, but the confirmation behavior is well disclosed.

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 compact clauses, both front-loaded: the core action and scope come first, followed by the discovery reference and confirmation gating. Every element earns its place.

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 no output schema, the description covers the essential context: what it does, who receives the invitation, how to find one, and the confirm-gated preview behavior. It could say more about what accepting or declining changes, but nothing needed to call it correctly is missing.

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 coverage is low at 33%, with only the confirm parameter described in the schema. The description compensates partially by naming the discovery tool for invitationId and by implying accept controls accept vs. decline, but it does not add format or meaning beyond that. Baseline 3 is appropriate given the partial compensation.

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: 'Accept or decline an invitation addressed to the coach.' It also scopes the invitation type with an example and points to the sibling tool get_my_pending_org_invitations, so an agent can distinguish this from send_invitation, invite_coach_to_organization, and list_invitations.

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?

Clear context is given: this is for invitations addressed to the coach, and the discovery tool get_my_pending_org_invitations is named. It does not explicitly state exclusions or contrast with alternatives beyond the discovery reference, so it is strong but not fully explicit.

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