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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered structurally. The description adds that only the caller's own membership is affected, but says nothing about consequences: whether entries/history are preserved, what happens if the caller is the owner, or that rejoining requires a new invitation.

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?

A single front-loaded sentence with no filler; the scoping qualifier ('own access ... they collaborate on') is placed where it does the most work.

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?

Output schema and rich annotations relieve the description of explaining return values and safety. However, for a destructive, non-idempotent membership mutation it omits key edge cases (owner cannot leave, effect on shared entries, need to be re-invited), so it is only minimally sufficient.

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?

Only one parameter and the schema documents it at 100% coverage, including the owner/name format and the unpinned-credential default. The description adds no meaning beyond that, which is acceptable at this coverage level but leaves nothing extra.

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 ... access to a ledger') plus the scope that matters: the authenticated user's own access, on a ledger they collaborate on. This implicitly separates it from deleteLedger and removeLedgerCollaborator, though it never names those siblings, so an agent must still infer the boundary.

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 context of use is implied by 'a ledger they collaborate on,' but there is no explicit when-to-use/when-not rule and no routing to removeLedgerCollaborator (removing someone else) or deleteLedger (deleting the whole ledger). Usage is inferable but not guided.

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