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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real operational context the annotations cannot convey: revocation is instant because the gate re-reads the allow list live on the viewer's next request, and removing a domain does not revoke addresses shared individually. It stops short of covering idempotency or error behavior for repeat/absent entries.

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 with no filler; the core action is front-loaded and the timing and edge-case notes follow in order of importance.

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 no explanation, and the description covers action, timing, and the domain-vs-address edge case. It omits what happens when the entry was never shared (error vs. silent no-op) and whether project ownership is required, which for a destructive, non-idempotent operation would be worth one more clause.

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%, and the schema for 'email' already spells out the address-or-domain form, so the description adds little there. Its only extra value is behavioral (domain removal leaves individually shared addresses intact), which is not a parameter-syntax clarification, 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: 'Remove one email, or one domain ... from a spawnpoint project's allow list.' The scope (single entry vs. domain) is explicit, and the inverse relationship with share_project is unmistakable without opening either 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?

The description clarifies what a call accomplishes but never states when to prefer it over alternatives or names the sibling tool (share_project) that performs the opposite action. Usage is implied rather than routed.

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