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

With annotations already indicating non-readonly and non-destructive behavior, the description adds valuable context: the invite is not immediately active; it requires a multi-step verification process and yields a one-time token. This goes beyond the basic write operation implied by the annotations, though it doesn't mention side effects like email sending or expiration behavior.

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?

Two sentences, no filler. The first sentence delivers the core purpose and outcome, the second clarifies the required subsequent flow. Every word earns its place.

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?

The description is sufficient for an agent to understand the tool's role in a larger workflow, especially with an output schema present. It explains the acceptance constraint and identifies the dependent tools. It doesn't exhaustively cover all edge cases, but for a creation tool with 6 parameters, it provides the essential context without redundancy.

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 the schema fully documents each parameter. The description adds no parameter-specific guidance beyond the overall purpose. This meets the baseline for well-documented schemas but provides no additional semantic layer.

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 action: 'Invite a team member to this company' and the key output: 'return a one-time MCP accept token'. It distinguishes itself from sibling tools by naming the subsequent verification steps (accept_team_invite_request, accept_team_invite_verify), positioning this as the initial creation step.

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?

It provides clear workflow context by explaining the required verification flow through sibling tools, which implies when this tool is used (to create the invite before verification). However, it does not explicitly state when not to use it (e.g., for existing team members) or contrast with alternative invite methods.

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