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

Annotations already convey idempotency and non-readonly/non-destructive status. The description adds meaningful behavioral context beyond that: the operation is asynchronous, requires member eligibility, has the same limits/idempotency as speedbot_invite, and explicitly excludes free-form messaging, automatic acceptance, and payment. It does not contradict any annotation; it only adds useful detail.

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 short sentences front-load the core purpose and immediately add the eligibility requirement, behavioral parity, and exclusions. There is no filler, repetition, or irrelevant detail. Every sentence 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?

For a 4-parameter async action with no output schema, the description covers purpose, prerequisite, idempotency reference, and capability exclusions. It does not describe the async response or how to observe the outcome, and it does not mention the optional team_key parameter, but those are modest gaps given the schema's own description for team_key. Overall it is complete enough for correct selection and reasonably informed invocation.

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 low (25%), so the description should compensate, and it partially does: 'on behalf of one managed team member' clarifies agent_id, and the idempotency reference hints at client_invitation_id's role. However, it never directly explains target_agent_id or client_invitation_id, and team_key is left undocumented in the description. The parameter names are reasonably self-explanatory, but the description does not fully carry the semantic burden.

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 states a specific verb and resource: 'Send an asynchronous invitation on behalf of one managed team member.' This clearly differentiates it from the generic speedbot_invite flow and other invite/team siblings by adding the managed-team-member scope. The exclusions ('No free-form message, automatic acceptance or payment') further sharpen what the tool is and is not.

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 provides clear context: use this when inviting on behalf of a managed team member, and it flags the prerequisite ('Requires that member's eligibility'). It also compares behavior to speedbot_invite ('Same limits and idempotency'), giving the agent a useful reference point. It does not explicitly name when-not or alternative conditions, but the managed-member context makes the intended use reasonably clear.

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