aya_tarefas_listar

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

No annotations are provided, so the description carries the behavioral burden. It adds one useful scoping trait — the tool returns only detected tasks matching the T-XXXX pattern — but says nothing about what the list contains, whether it reflects current workspace state, or how 'detected' tasks are identified. For a read-ony listing operation the risk is low, but the disclosure is minimal.

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?

A single front-loaded sentence with the verb first and no filler; 'T-XXXX detectadas' adds specificity without verbosity. It is appropriately sized for a zero-parameter tool, though the phrasing is terse and slightly cryptic.

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 clarify what the call returns and what 'T-XXXX detectadas' means as a detection source, but it does neither. An agent invoking this tool is left unsure about return format, scope, and how the task list is produced.

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?

The tool has zero parameters with 100% schema coverage, so there is nothing the description needs to add about inputs. The T-XXXX mention relates to the content of the result, not to parameter semantics, and no parameter explanation is required.

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 states a specific verb and resource: 'Lista tarefas T-XXXX detectadas' (lists detected T-XXXX tasks). The T-XXXX pattern gives an agent useful scoping information and helps distinguish this from other list tools like aya_testes_listar or aya_requisitos_listar, though it does not explicitly contrast with task-centric siblings such as aya_tarefas_proxima.

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 when-to-use or when-not-to-use guidance is provided. An agent must infer from the name alone when to pick this over related task tools like aya_tarefas_proxima, aya_tarefas_validar_dependencias, or aya_tarefas_detectar_ciclos; there are no exclusions, prerequisites, or alternatives mentioned.

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