zyta_expedientes_tareas_list

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

No annotations are provided, so the description carries full burden. It only states 'GET', implying read-only, but does not disclose behavior like pagination limits, sorting, or whether filters are mandatory. No information about destructive actions or authentication requirements.

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 redundancy. It is front-loaded with the key action. However, it could be slightly longer to cover missing behavioral cues without losing conciseness.

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?

With no output schema, the description should at least indicate the response structure. It does not mention pagination, sorting, or whether the response lists tasks, deadlines, or both. For a 5-parameter tool, this is insufficient.

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 60% (estado and prioridad lack descriptions). The description adds no meaning beyond the schema. It does not explain the enum values or how they interact. An agent would need to infer usage from names alone.

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 tool lists deadlines/tasks of a case file (expediente), using the verb 'Lista' and resource 'vencimientos/tareas'. Sibling tools like zyta_expedientes_tareas_create and zyta_expedientes_alertas_list help distinguish it, but the description could be more precise about whether it lists both deadlines and tasks or just tasks.

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 explicit guidance on when to use this tool versus alternatives such as other list tools. The description does not mention prerequisites, filters, or conditions for use. The agent must infer from naming conventions.

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