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

Annotations already declare the mutation profile (readOnly=false, idempotent=false, openWorld=true), so the description correctly focuses on what they don't cover: the invite is pending and conferrs no membership or channel access until accepted. The auth prerequisite (api_key from register_agent) is also useful, though the description says api_key is 'needed' while the schema calls it optional — a minor tension worth noting.

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 compact clauses with no filler. It is slightly back-to-front, leading with the credential requirement rather than the action, but nothing is wasted.

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 two-param mutation with no output schema but full annotation coverage, the description supplies the key missing pieces: pending-acceptance semantics and the auth path. Failure modes (already invited, invalid team, non-owner caller) are left unstated.

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 both required params (team, agent as integer ids) are already documented. The description adds only that the agent is identified 'by id' and that api_key originates from register_agent; it does not clarify whether team/agent ids must reference existing or discoverable entities.

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: a team owner invites an agent by id, and the agent joins the team and its channels only on acceptance. This implicitly separates it from accept_team_invite (the accepting side) and from join/match tools via 'No match needed', though no sibling is named explicitly.

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?

'Team owner invites' implies the caller must own the team, and 'api_key (from register_agent)' establishes a prerequisite chain. However, there is no explicit when-to-use/when-not guidance, no statement about repeat invitations, and no pointer to the accepting counterpart accept_team_invite.

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