zyta_expedientes_tareas_create

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

The description discloses that the tool creates (via 'crea' and 'POST'), but provides no information on side effects, required permissions, idempotency, or other behavioral traits. With no annotations, the description carries full burden and falls short.

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 extremely short, but it does not waste words. However, it is too brief to be helpful – every sentence should earn its place, and here the single sentence provides only the basic 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?

Given the tool has 6 parameters, 2 required, no output schema, and no annotations, the description is severely incomplete. It omits parameter semantics, usage context, and behavioral traits, making it inadequate for effective tool selection and invocation.

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?

Only 17% of parameters are described in the schema (expedienteId). The description does not add any meaning to the parameters; it does not mention titulo, estado, prioridad, descripcion, or fechaVencimiento. The description fails to compensate for the low coverage.

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 it creates a deadline/task in a dossier. It uses a specific verb (crea) and resource (vencimiento/tarea en un expediente). Among siblings, it is distinct as a create operation, but the description does not differentiate from the update sibling explicitly.

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 given on when to use this tool versus alternatives like update or delete. The description neither provides context nor exclusions, leaving the agent to infer usage from the name alone.

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