Listar tareas

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is clear. The description adds that the tool supports filters, but does not disclose behavior like default return of all tasks, pagination, or permission requirements. Minimal added value beyond annotations.

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 concise sentence that front-loads the action 'Lista tareas'. Every part is relevant, though it could be slightly more structured. No unnecessary information.

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 9 parameters, no output schema, and no annotations beyond safety hints, the description is too brief. It does not explain return format, pagination, interaction of multiple filters, or whether no filters returns all tasks. For a tool with this complexity, more guidance is needed.

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 78%, and many parameters have descriptions like 'BeeboleId (ObjectId, 24 hex)' or 'Unix timestamp en MILISEGUNDOS'. The tool description lists filter categories (e.g., 'responsable', 'rango') that map to schema parameters, adding some contextual meaning but not significantly beyond the schema.

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 lists tasks with specific filters (proyecto, estado, responsable, etc.), distinguishing it from other list tools like beebole_list_persons or beebole_list_projects. The verb 'Lista' and resource 'tareas' are explicit.

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?

The description implies usage for filtering tasks but lacks explicit guidance on when to use this tool versus alternatives like beebole_get_task for a single task or other list tools. No exclusions or prerequisites are mentioned.

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