post_team_members

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true. The description adds no behavioral context beyond these hints—it does not mention the destructive nature, idempotency, required permissions, side effects, or what happens if a user is already a member. It does not contradict the annotations, but it fails to add any value.

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?

The description consists of two sentences that convey identical information. The second sentence ('Add one or more users as members to a team') is pure repetition of the first, violating the principle that every sentence should earn its place. While it is front-loaded, the redundancy makes it inefficient.

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 destructive mutation tool with nested required parameters and no output schema, the description is far too thin. It omits any warning about destruction, permission requirements, return behavior, or usage context, leaving the agent to rely entirely on the schema and annotations. The description does not provide the contextual completeness expected for this complexity level.

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% at the top level, so the description should compensate for parameter meaning. It vaguely mentions users and a team, but does not clarify the path/body structure, the teamId parameter, or the format of user identifiers. It only partially hints at the 'users' array without adding useful syntax or constraints.

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 'Add members to a team. Add one or more users as members to a team.' is essentially a restatement of the tool name post_team_members. It adds only the minor detail that multiple users are allowed, which is already implied by the plural name and schema. No sibling differentiation (e.g., from get_team_members or delete_team_member) is provided.

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 guidance on when to use this tool versus alternatives such as get_team_members or delete_team_member. No prerequisites, permissions, or context for adding members is mentioned. The description simply states the action without any usage framing.

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