evidence_delete

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'delete' without noting that deletion is destructive/irreversible, whether permissions are required, or any cascading effects. For a mutating tool this is a notable gap.

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, front-loaded sentence with no filler. Every word contributes to stating the tool's core purpose.

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 parameter schema and output schema carry much of the needed operational detail, making the tool minimally usable. However, the complete absence of deletion semantics and usage guidance leaves an agent uncertain about important selection and safety aspects.

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 description coverage is 100%, so the schema already explains all four parameters. The description adds only the 'any evidence' scope, which slightly reinforces the evidence parameter but provides no extra operational meaning such as id/kod precedence or company behavior.

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 a specific verb and resource: 'delete a record from any AbraFlexi evidence.' This is clear and distinct from unrelated tools, but it does not differentiate the generic evidence_delete from specialized sibling deletes like contact_delete, invoice_issued_delete, or product_delete.

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 is provided on when to use this generic delete versus the specialized delete tools, nor are there any exclusions or alternative recommendations. The 'any evidence' phrasing implies broad applicability, but the agent is left to infer routing on its own.

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