executions_attachments_list

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

With no annotations, the description provides behavioral context: it mentions that items with `uploaded=true` include a pre-signed `downloadUrl` with 300s expiry. This adds value beyond the input schema. However, it does not disclose potential pagination, ordering, or read-only behavior.

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 short and front-loads the purpose. The tag line 'Tag: Execution Attachments' and the Portuguese sentence add minor redundancy, but overall it is efficient and well-structured.

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?

For a simple list tool with no output schema, the description covers the core functionality and key detail about download URLs. It is adequate but could be more complete by mentioning pagination, ordering, or handling of empty results.

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% (only one parameter, 'id', described as Execution ID). The description does not add any additional meaning or constraints to the parameter, so it performs at baseline.

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 execution attachments', a specific verb-resource pair. It distinguishes from sibling tools like executions_attachments_create and bugs_attachments_list, making the tool's purpose 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?

The description implies usage for listing attachments of a specific execution, but lacks explicit guidance on when to use it vs alternatives, when not to use it, or any prerequisites.

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