zyta_expedientes_delete

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

Discloses cascade deletion ('cascada') and exclusion of synced causes. Without annotations, this provides adequate behavioral insight, though could mention irreversibility or permissions.

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?

Extremely concise with two sentences, no fluff, all information contributes to understanding.

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?

For a simple delete tool with one parameter, the description is mostly complete: it explains what is deleted, the cascade behavior, and what is not deleted. Could mention return value or error conditions, but not critical.

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 is 100%, so baseline is 3. The description does not add new information about the 'id' parameter beyond what the schema already provides ('UUID de la causa sin portal').

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 action ('Elimina una causa sin portal y sus actuaciones') with the verb 'elimina' and resource 'causa sin portal', and distinguishes from siblings by specifying it does not delete synced causes from PJN/MEV/CABA.

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 explicit when-not-to-use: 'No borra causas sincronizadas desde PJN/MEV/CABA.' However, it lacks a positive statement of when to use, though the purpose inherently clarifies its context.

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