delete_company

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

No annotations, but description discloses soft-delete behavior and return format. Does not cover permissions, side effects, 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?

Three concise sentences, front-loaded with action, each sentence adds unique value (action, context/mirroring, return format). No redundancy.

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?

Covers core behavior and output, but lacks parameter explanations and error scenarios. Adequate given simplicity but incomplete for parameter semantics.

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 0%; description does not explain company_id or account_id parameters beyond the return example. No guidance on when or why to use account_id.

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 explicitly states the action as 'soft-delete' with clear effects ('Status flips to disabled, records retained'), specifying the resource (company) and distinguishing it from hard deletion.

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?

Provides usage context: mirrors delete_tracker semantics and advises using list_companies(status='active') afterward. Lacks explicit when-not-to-use or alternatives like update_company.

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