Remove Current Project (Company)

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

Description adds value beyond annotations by emphasizing permanence and irreversibility. It also lists required parameters and provides the API endpoint. No contradiction with annotations.

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 somewhat repetitive (e.g., 'cannot be undone' stated twice). Includes API endpoint info which adds length but is useful. Could be more concise.

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 no output schema, the description should explain the response or error behavior, which it lacks. Also missing details on preconditions or side effects beyond deletion.

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 basic descriptions. The description merely repeats required parameters without adding semantic 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 states the specific action (permanently delete) and resource (Equipment records), differentiating from just 'remove project'. However, the tool name 'remove_current_project_company' suggests removing a project, causing potential confusion, but the description clarifies the actual resource.

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 only states the tool's action without any guidance on when to use it versus alternatives (e.g., other equipment removal tools). No exclusions or context for selection.

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