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

Annotations already declare readOnly=false, destructive=false, idempotent=false, and openWorld=true. The description adds only that this joins an invited team and where the ID comes from; it does not explain permissions, side effects, or behavior when already a member, but with annotations present a 3 is appropriate.

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 short sentences, purpose first and ID source second; there is no filler or redundant restatement of the title.

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 one-parameter action with full schema coverage and annotations, the description covers the precondition and parameter source. It does not address return or error behavior, and the ID-source inconsistency weakens it slightly, so it is nearly but not fully complete.

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 coverage is 100% and the schema already documents teamId as 'Team ID from list_teams.' The description adds a source, but says list_team_invitations, creating an inconsistency with the schema's list_teams source that could confuse an agent even though the invitation-list source is arguably more relevant.

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 uses a specific verb ('Join') and resource ('a team'), and the clause 'the user was invited to' scopes it to accepting an existing invitation rather than creating or inviting to a team. It does not explicitly name sibling alternatives, so it is clear but not fully differentiated.

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 gives the triggering condition ('user was invited') and the source for the required ID ('list_team_invitations'), which tells an agent when and how to use it. It does not state exclusions or what to do if no invitation exists.

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