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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the destructive nature is covered. The description adds the consequence that the invitation link stops working, which is useful beyond the annotations. However, it does not discuss reversibility, permissions, or side effects.

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?

The description is two short sentences and front-loads the action. The second sentence somewhat repeats the first but adds the scope and consequence, so it mostly earns its place. There is minor redundancy but no bloat.

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 simple mutation tool with full schema coverage and clear annotations, the description provides adequate purpose and effect. Missing details like prerequisites or behavior when the invite is already revoked are minor for this tool's complexity.

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%, with both parameters documented directly in the schema. The description adds no additional syntax, format, or meaning for the 'id' or 'business' parameters. Baseline 3 is appropriate when the schema fully carries parameter semantics.

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 a specific verb (withdraw/revoke), resource (open invitation), and scope (one managed business). It clearly distinguishes the action from invite creation, though it does not explicitly name the sibling invite tool. The outcome 'link stops working' adds useful specificity.

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 description gives no explicit when-to-use guidance or alternatives. It does not say when this tool should be chosen over related tools like agenta_businesses_invite or agenta_businesses_id_link. Usage is only implied by the action name and title.

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