taiga_epics_attachments_list

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

No annotations are provided, so the description carries the burden. It only states the operation (list) without disclosing read-only nature, permission requirements, pagination, or return structure, leaving the agent uncertain about side effects and response shape.

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, front-loaded sentence with no wasted words, precisely stating the action and target resource.

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?

Without an output schema or annotations, the description offers minimal context. It does not describe the response format, possible fields, pagination, or any special behavior, which is insufficient for an agent to fully predict the tool's output.

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 100% with 'Project ID' and 'Epic ID' clearly described. The description adds no extra parameter detail, so baseline 3 is appropriate as the schema handles the parameter semantics.

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 'List attachments of an epic.' uses a specific verb (List) and resource (attachments) scoped to 'epic', clearly distinguishing it from sibling tools like taiga_epics_attachment_get (single attachment) and other resource-specific attachment listers (user stories, tasks, issues, wiki).

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 is provided on when to use this tool versus alternatives. It does not mention that it lists all attachments for an epic, nor does it differentiate from taiga_epics_attachment_get or other attachment list tools.

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