mirlo_list_tasks

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

No annotations exist. Description indicates a read operation but does not mention pagination, sorting, rate limits, or any behavioral traits beyond listing.

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?

Single sentence, concise, no fluff. All words add value.

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 8 parameters, no output schema, and no annotations, the description is too minimal. Missing details on pagination, sorting, default behavior, and response format.

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 38% (3 of 8 params described). Description mentions filter types (assignee, status, due date, entities) adding context to some params (e.g., owner_id, is_completed) but leaves others (type, limit, priority, deal_id, ticket_id) without extra meaning.

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?

Clearly states verb 'List' and resource 'tasks', and distinguishes from siblings (create, complete). Mentions filtering by assignee, status, due date, and associated entities.

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?

Implied usage: use when needing to list tasks with filters. No explicit when not to use or alternatives among siblings provided.

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