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

Goes beyond the annotations by disclosing the permission gate (owner/admin only) and the concrete effects: the link stops working and the address becomes invitable again. It does not explicitly state irreversibility or that other pending invites are untouched, but the effect description is unusually informative for a mutation tool.

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 tight sentences, front-loaded with the action and permission requirement, followed by effect and ID sourcing. No filler or restatement of the title.

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?

With an output schema present and annotations covering the safety profile, the description supplies everything else an agent needs: authorization requirement, the observable consequences of the call, and where to obtain the required identifier.

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 schema already documents slug, org_id, and invite_id with their sources. The description only repeats the invite_id provenance already present in the schema, adding no new parameter meaning, 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 and resource ('Cancel an outstanding organization invite') plus scope qualifier ('outstanding'). This clearly separates it from siblings like findagent_resend_invite and findagent_invite_member without needing to open 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?

Gives a concrete when-to-use scenario (invite sent to the wrong address that otherwise blocks the correct one indefinitely) and states the owner/admin prerequisite. It stops short of explicitly contrasting with findagent_resend_invite, the nearest alternative, so an agent must infer that distinction.

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