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

With no annotations, the description carries the full burden and delivers two real behavioral facts the schema does not: the reason becomes public, and the invitation is not consumed. What's missing is any statement of side effects toward the inviter or whether a decline can be revised to an acceptance later.

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 sentences, nothing redundant, and the core action is stated first. The terseness borders on cryptic but every sentence carries 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?

A three-parameter mutation tool with no annotations and no output schema needs the description to convey outcome and side effects. It covers the invitation's persistence and reason visibility but says nothing about the response, the inviter's view, or how acceptance would differ.

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%, so all three parameters (name, reason, secret) are already documented in the schema. The description adds no additional constraint or format meaning beyond that, so the baseline 3 applies.

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 (decline) and its object (the invitation to add an element), which is a clear operation an agent can pick out. It's less explicit about which sibling invitation-flow tool it complements, but the action itself is unambiguous.

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 invitation stays open' implies this is a non-committal refusal and that no cleanup is needed, which signals the usage context implicitly. There is no explicit statement of when to decline versus simply ignoring the invitation, nor a named alternative.

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