set_project_members

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), the description adds meaningful context: removing a member does not delete their work or affect their account. This clarifies the tool's side effects and safety profile, though it could further detail behavior on role changes.

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 two sentences, front-loaded with the primary action, and every sentence provides essential information. No unnecessary words or repetition.

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 main actions, a prerequisite, and a key behavioral guarantee. With a complete input schema and output schema present, the description is sufficiently complete for a membership management tool, though it could mention that multiple people can be processed simultaneously.

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?

The schema descriptions already fully cover all three parameters (role, people, project_id) at 100%. The tool description does not add parameter-specific details beyond the overall action, which is adequate given the schema's thoroughness.

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 clearly specifies the tool's function: adding people to a project, changing their roles, or removing them. This distinguishes it from related tools like assign_people/unassign_people, which operate at the task level.

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 description notes that membership rights are required, providing a prerequisite for use. However, it does not explicitly differentiate when to use this tool versus alternatives like assign_people or unassign_people, leaving the usage context implicit.

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