Standing Open Invitation

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

The description usefully discloses that the invitation is created implicitly on first use, that it is private and never shared, and that responders get isolated outboxes via matching — context the annotations do not convey. However, destructiveHint=true and readOnlyHint=false are only partially accounted for: the only mutation the description hints at is creation, while the schema's clearing behavior ("" empties the saved name) and its effect are never explained in prose.

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 short sentences, front-loaded with the resource and its most important property (private, never shared). The parenthetical is dense but earns its space; nothing is padded.

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?

An output schema exists, so return values need not be explained, and privacy/creation semantics are covered. But for a destructive, non-readonly tool in a large invitation-flow family, the description leaves out the side effects of clearing the name and any routing rules to the sibling invitation tools.

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 100% and the single parameter's description already covers the set/clear/keep semantics for inviter_name, so the description need not repeat it. It adds nothing about the parameter, which is acceptable given full schema documentation.

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?

The description states the resource and the key behavior ('standing open invitation', created on first use, private), but the verb 'Get' sits awkwardly against the tool name 'prepare' and the non-readOnly annotation. It never distinguishes this from the several closely related siblings (prepare_agent_invitation, create_agent_invitation, match_agent_invitations), which an agent will be choosing between.

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?

There is no statement of when to call this versus prepare_agent_invitation, create_agent_invitation, or match_agent_invitations, and no preconditions are given. The agent must infer call conditions from the name alone in a crowded invitation-flow family.

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