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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the safety profile is covered. The description adds nothing on top of that: it says nothing about required permissions, what happens if the user is already a member, or the consequences of the destructive flag. No value is added beyond structured fields.

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?

A single short sentence, front-loaded with the action, with zero filler words. It is tight and well-structured, though its brevity reflects under-specification rather than genuine economy of information.

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 simple two-parameter add operation whose annotations already cover the safety profile, the description is minimally sufficient. Still, with 0% parameter coverage and no behavioral notes, an agent lacks the detail needed to call it confidently in edge cases (e.g., duplicate membership).

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% for both required parameters, so the description must carry the burden and does not. 'A person' and 'a team' loosely gesture at user_id and team_id but provide no format, constraint, or semantics; the agent learns nothing about the two integers beyond the schema types.

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 sentence names a clear verb (add) and resource (person to a team), so the action is understandable. However, it is essentially a natural-language restatement of the name/title 'add_team_member' and offers no differentiation from siblings like add_inbox_member or update_agents_in_team. It sits between a vague purpose and a differentiated one.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. With siblings such as add_inbox_member, remove_team_member, and update_agents_in_team present, the agent gets nothing to help choose among them.

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