Bulk Remove Company Users From Projects

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

Annotations already indicate destructiveHint=true. The description reinforces irreversibility and bulk nature. It adds the API endpoint info but does not disclose additional behavioral traits like authentication needs or rate limits.

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 repetitive, stating the action twice ('Use this to delete...' and 'Removes...'). It is front-loaded but could be more concise by removing duplication and extraneous API details.

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?

Given the schema coverage and no output schema, the description adequately explains the bulk removal intent and required params. However, it does not clarify expected responses or error conditions, leaving minor gaps.

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 input schema already describes both parameters with 100% coverage (company_id and users). The description only lists the required names, adding no new meaning beyond the schema.

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 tool's action: 'allows company users to be bulk removed from multiple projects' and 'delete many Directory records'. It distinguishes from sibling tools like 'bulk_add_company_users_to_projects' by specifying removal and irreversibility.

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 advises using this tool for bulk removal and warns it cannot be undone. However, it lacks explicit when-not-to-use guidance or comparisons with alternative tools like 'bulk_remove_project_memberships'.

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