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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false) it discloses the auth model, the default role applied, the sign-up email side effect, and the full set of per-email outcomes (INVITED, ALREADY_MEMBER, ALREADY_INVITED, FAILED with failureReason). This is exactly the extra context annotations cannot carry.

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?

Front-loaded with the action and effect, then layered with prerequisites and return values. The second sentence is dense and slightly run-on, packing auth, bot binding, and the CLI restriction together, but no sentence is filler.

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 write tool with no output schema, the description covers the mutation's effect, auth requirements, side effects, and the return shape. Nothing an agent needs in order to call it safely is missing.

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% so the baseline is 3, but the description adds meaning: the binding-argument path that supplies botId/projectApiKey for bot callers, and the user-confirmation constraint that governs the emails array. It stops short of adding syntax or format detail for individual fields.

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 ('Invite teammates (by email) to the TestChimp organization'), the effect ('so they can access this project'), and the resulting role ('joins as a Viewer'). No sibling tool shares this action, so an agent can route to it unambiguously.

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 explicit conditions: requires an OAuth user session whose user is an org admin, QA bots must go through the connector with binding arguments, and the CLI --bot key cannot invite. It also names the exclusion ('Only call with emails the user explicitly confirmed') and points to teamSettingsUrl for role changes/seats.

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