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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description isn't carrying the safety profile alone. It still adds real context: the non-deletion of the personal account, the optimistic-concurrency requirement on membership version, and a recovery step ('inspect the team after an uncertain response'), though it stops short of stating permission requirements or what a conflict response looks like.

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, front-loaded with the action, then the scope limit, then the verification advice. Nothing is redundant with the sibling names or the schema.

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 destructive three-parameter mutation with annotations covering safety and no output schema, the definition covers action, side effects, concurrency, and a post-failure check. A minor gap is the absence of guidance on what to do for a stale expectedVersion beyond the schema's 'refresh after a conflict' note.

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 baseline is 3; the schema already documents all three parameters with ID patterns and version sourcing. The description reinforces that the version is the 'current' membership version but adds no format or conflict-resolution detail beyond what the schema says.

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 ('Remove a member's Company access') and immediately bounds the blast radius ('does not delete their personal Publora account'), separating it from invite/revoke-invitation siblings. An agent knows exactly what this tool mutates without opening the 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?

Usage is implied by the offboarding framing plus 'Confirm the selected member and inspect the team after an uncertain response', which is operational advice rather than selection guidance. It never names alternatives such as company_revoke_invitation (pending invites) or company_transfer_ownership, so the agent must infer when this tool is preferred over those.

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