basecamp_manage_project_people

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

With no annotations, the description carries the full burden of behavioral disclosure. It implies mutation (grant/revoke) but does not mention any side effects, permission requirements, reversibility, or behavior when both grant and revoke arrays are provided. This is a significant gap for a management tool.

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 a single, front-loaded sentence with no filler words. It is maximally concise and clear at a surface level.

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?

This is a mutation tool with moderate complexity (arrays for grant/revoke) and no output schema. The description omits crucial context like whether both grant and revoke can be used together, what happens on failure, or required fields. It is too minimal for an agent to invoke correctly without additional assumptions.

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 67% (grant and revoke have descriptions, project_id does not). The description adds little beyond reiterating 'grant' and 'revoke', and it does not clarify the format or purpose of project_id or the person IDs. Since coverage is not high and the description does not compensate, the meaning of parameters remains incomplete.

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 states the action ('grant or revoke') and the resource ('project access for people'), which distinguishes it from sibling tools like listing or getting people. It is specific about the operation, though it could more explicitly mention project_id.

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?

No guidance is provided on when to use this tool versus alternatives, such as when to use list_people to check current access or create_project to set initial membership. The description simply states the action without context or exclusions.

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