list_tasks

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

No annotations are provided, so the description bears full responsibility. It only mentions three filters (status, agent, phone) but the schema includes eight more (e.g., limit, offset, priority). It does not disclose reading behavior, pagination, or result ordering. The description oversimplifies the tool's capabilities.

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 line that is concise but omits critical details. The hyphen separation is clear, but the '[query]' suffix appears to be a placeholder and reduces clarity. It is not fully optimized for agent 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?

Given the rich input schema (11 parameters) and no output schema, the description should cover essential aspects like pagination, default limit, and the purpose of less obvious parameters. It only highlights three filters, leaving agents uninformed about other options like due_date, priority, and include_completed.

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?

With 91% schema description coverage, the schema already documents parameters well. The description only lists three filters, adding minimal new meaning beyond what the schema provides. Baseline 3 is appropriate.

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?

Description clearly states it lists tasks with optional filters by status, agent, or phone. The verb 'listar' is specific to listing, and the resource 'tasks' is distinct from many sibling tools. However, the appended '[query]' is ambiguous and may confuse agents.

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 on when to use this tool versus alternatives like search_conversations or list_agents. No mention of when not to use it or prerequisites.

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