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

Beyond the annotations, it discloses that memberUuids replaces the existing membership rather than appending, which is critical destructive behavior. It also states the required MANAGE_TEAMS permission and teams:write API-key scope.

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 is short, front-loaded, and every sentence adds useful information. The NOTE about memberUuids is placed prominently where an agent will notice it before acting.

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?

The description covers the critical invocation details: optional-field behavior, destructive membership replacement, alternatives, permissions, and scope. With no output schema, it does not describe the return value, but the core invocation guidance is otherwise 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%, so the schema already documents all parameters in detail. The description adds meaningful emphasis on the destructive replacement semantics of memberUuids and the fact that all fields are optional, but it does not clarify the other parameters beyond what the schema already provides.

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 states a specific verb and resource: it updates a team's metadata or replaces its full member list. It also distinguishes the membership-replacement behavior from the sibling tools pm_add_team_member and pm_remove_team_member.

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 explicitly says to use pm_add_team_member / pm_remove_team_member for incremental membership changes, and clarifies that only specified optional fields change. This gives clear when-to-use and alternative guidance.

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