Remove Current Project (Project)

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

The description claims it 'permanently deletes Equipment records,' but the endpoint and parameters indicate it removes the current project association from an equipment item. This misrepresents the actual behavior. Annotations correctly set destructiveHint=true, but the description is misleading beyond that.

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 contains redundant statements ('This cannot be undone' appears twice, and 'Permanently removes the specified Equipment records' is repeated). It could be more concise without losing meaning. Front-loaded with a confusing purpose statement.

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?

Missing output schema, and the description fails to explain what 'remove current project' actually means in context. For a destructive operation, it should clarify the scope (e.g., only the project association is removed, not the entire equipment record). Incomplete for safe agent invocation.

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?

All three parameters are fully described in the schema (100% coverage). The description only repeats that they are required, adding no additional semantic context 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 'Remove current project (Project)' and then says 'Use this to permanently delete the specified Equipment records,' creating ambiguity about whether it removes a project association or deletes equipment records. The endpoint suggests it removes the current project link, but the description focuses on deleting records, leading to confusion.

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 on when to use this tool versus alternatives like 'associate_equipment_with_project_project' or 'bulk_remove_current_project_project.' The description simply states to use it for deleting equipment records 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.