delete_users

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Delete a row' implies mutation but does not mention irreversibility, potential cascade effects, required permissions, or behavior when the row does not exist. This is a significant gap for a deletion tool.

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, front-loaded with the verb 'Delete,' and contains no unnecessary words. It is perfectly concise and well-structured.

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?

While the tool is simple with one parameter and has an output schema, the description lacks key contextual details such as whether the deletion is permanent, what happens if the row is referenced by other tables, or how errors are surfaced. Given no annotations, the description is too sparse for a mutation tool.

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 schema has one parameter (row_id) with no description in the schema (0% coverage). The description adds that deletion is done 'by id,' clarifying that row_id is the identifier to match. However, it does not provide additional constraints or context beyond the parameter name, so the compensation is partial.

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 'Delete a row from users by id' clearly states the action (delete), the resource (users), and the targeting mechanism (by id). It distinguishes itself from sibling CRUD tools like get_users, create_users, and update_users.

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?

Usage is implied by the description and tool name, but there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The agent can infer it is for deleting a user row, but no direct 'when to use' or 'when not to use' is provided.

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