Listar Tarefas do Ekyte

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

Annotations indicate safe read-only operation; description adds critical behavioral details: API does not paginate, MCP applies client-side pagination after filters. Also lists return fields. No contradictions.

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?

Description is well-structured with clear sections: purpose, filter types, pagination, tip, return fields. It is front-loaded and concise, though a bit long with repeated sentences about filter types. No wasted words.

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 12 parameters (all documented in schema), no output schema, and clear annotations, the description covers behavioral nuance (pagination, filter scope), cross-references to discover IDs, and return fields. It is comprehensive for an agent to use effectively.

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 100%, so baseline is 3. Description adds value by classifying filters as server-side vs client-side, providing example values (e.g., 'playbook' for search), and explaining pagination parameters. This goes beyond schema descriptions.

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, and the title 'Listar Tarefas do Ekyte' is specific. It distinguishes from sibling tools like ekyte_list_project_tasks by being company-wide and listing workspace filter. Purpose is unambiguous.

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?

Explicit guidance on filtering by workspace_id to reduce volume, cross-references to ekyte_list_workspaces, and explains server-side vs client-side filter behavior. Also mentions default status filter. No explicit when-not-to-use but overall very helpful.

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