Bulk Remove Current Project (Project)

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds emphasis on irreversibility ('cannot be undone') but does not provide additional behavioral traits beyond what annotations already convey.

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 but contains redundancy: 'Permanently removes... This cannot be undone' is repeated verbatim. The first sentence adds little value beyond the title.

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 simple destructive bulk operation with good annotations and schema coverage, the description adequately covers the action, irreversibility, required parameters, and API endpoint. Minor gaps (e.g., no mention of success/error conditions or permissions) are acceptable given the tool's simplicity.

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?

Input schema has 100% coverage with clear parameter descriptions. The description only restates that project_id and company_id are required, 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 bulk removes and permanently deletes Equipment records in the current project context. It distinguishes from siblings like bulk_remove_current_project_company and remove_current_project_project by specifying the resource (Equipment records) and scope.

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 provides usage context ('Use this to permanently delete the specified Equipment records') and lists required parameters, but does not explicitly compare to alternatives (e.g., singular remove or other bulk delete tools) or state when not to use it.

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