acr_list_tasks

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

No annotations are provided, so the description carries the full burden. It only states 'List tasks' without disclosing read-only nature, pagination, permissions, or side effects. This is insufficient for a tool with no 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 very short and front-loaded with the action. It wastes no words, but the 'Args:' section is slightly informal. Overall, it is concise and efficient.

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?

The output schema is present, so return values are covered. However, the description lacks context such as prerequisites (e.g., registry must exist), what constitutes a 'task' (e.g., ACR tasks for automated builds), and does not elaborate beyond the basic operation. It is adequate but not thorough.

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 0%, so the description must compensate. It adds brief explanations ('Resource group name', 'Name of the container registry') that clarify the parameter names but are minimal and lack constraints or format details.

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 'List tasks in a container registry,' which uses a specific verb and resource. It distinguishes the tool from sibling tools like acr_create_task, acr_delete_task, and acr_run_task, which perform different actions on tasks.

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 explicit guidance on when to use this tool vs alternatives is provided. The purpose is straightforward, but there is no mention of when to prefer this over other list tools like acr_list_builds or acr_list_repositories. Implicit usage is clear for listing tasks, but lacks exclusion criteria.

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