delete_employee

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

The description discloses the soft-delete behavior (make inactive), which is a key behavioral trait. However, it does not mention any side effects, authorization needs, or rate limits. With no annotations, the description carries the full burden, and this is partial.

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 a single sentence with no wasted words. It front-loads the core action and context. However, it could arguably include more detail without being verbose.

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?

The tool is simple but lacks output schema and annotations. The description does not mention what happens after deletion (e.g., response, success indication). It is incomplete for a tool that modifies data.

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 description adds no information about the parameters. Schema coverage is 50% (company is documented, params is not). For a low-coverage schema, the description should compensate, but it does not. The nested idOrEntity parameter is unexplained.

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 verb 'Delete' and the resource 'employee', and clarifies it's a soft delete (make inactive). It distinguishes itself from other sibling tools like create or update.

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. For example, it doesn't mention that updating the employee's status could achieve the same result. A user must infer context.

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