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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds meaningful behavioral context beyond that: every call creates an approval card, sends exactly once on approve, requires per-call manager approval, and has no standing grant. The 'do not re-ask in chat' note is particularly useful operational guidance.

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 dense but well-structured: the core action is front-loaded, followed by requirements, exclusions, routing, and sensitive-tier guidance. Every sentence adds operational value, and the formatting makes the approval behavior and routing easy to scan.

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 mutation tool with no output schema, this description is remarkably complete: it covers the action, prerequisites, required and optional fields, approval behavior, exactly-once sending, exclusions, and sibling-tool routing. An agent has everything needed to invoke it correctly.

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?

The input schema already has 100% coverage, clearly describing email, role, name, and companyId. The description reinforces the required/optional split and role presets ('team / manager'), but does not add significant new parameter-level meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 clearly states the verb and resource: 'Add one human teammate to the current company by email.' It also differentiates itself from sibling tools by explicitly routing AI agents to interview_for_hire and existing member checks to get_team_members.

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 says exactly when to use this tool ('not yet on get_team_members'), names the alternative for AI agents (interview_for_hire), and gives exclusions such as 'No bulk' and 'No permission designer.' It also explains the approval workflow and when to invoke the tool, leaving no ambiguity about routing.

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