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

Annotations already flag destructiveHint=true and readOnlyHint=false, so mutation is known. The description adds real behavioral context beyond that: accepting hands over the team secret and may activate the team, which tells the agent about state transitions and credential disclosure. It omits what rejecting does, holding it below 5.

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?

One front-loaded sentence with the action stated first and the consequence attached compactly. Nothing is wasted, though the parenthetical is a little dense.

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 3-required-param mutation with no output schema and no parameter documentation, the description covers the accept path well but leaves the reject path and the identity parameters unexplained. Adequate but with clear gaps.

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 0%, so the description must carry all parameter meaning. It does explain the 'accept' boolean's effect (secret handoff, possible team activation), but team_id and agent_id are left unaddressed in both schema and description.

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?

Names a specific verb pair and resource: accept or reject your assigned team role. The parenthetical adds the effect of accepting. It does not explicitly differentiate from siblings like ack_coordination or add_team_member, but the scope is unambiguous enough that an agent can identify it.

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 phrase 'your assigned team role' implies the trigger condition (you were offered a role), but there is no explicit when-to-use, no note about waiting for an invitation, and no mention of alternatives for declining or leaving later. Usage is inferable rather than stated.

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