List execution attachments

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

Annotation readOnlyHint=true already signals safe read operation. Description adds return-value context (metadata and download URLs), but does not disclose potential pagination, empty results, or permission requirements; still consistent with 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 second sentence is informative and concise, but the first sentence 'TestExecution.list_attachments' is redundant with the tool name. Overall it is short and front-loaded enough to be usable.

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 read-only list operation with one well-documented parameter, the description adequately indicates what is returned (metadata and download URLs). No output schema exists, so mentioning return payload is beneficial; minor gaps like empty-list handling are acceptable.

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 covers execution_id with description 'Test execution id' at 100% coverage, so the description adds little beyond schema. It does not elaborate on how to obtain the execution_id or format expectations, but baseline 3 is warranted.

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 explicitly says 'Returns attachment metadata and download URLs' for TestExecution, making the verb and resource clear. It does not explicitly contrast with sibling attachment-list tools for case/plan/run, though the tool name and 'TestExecution' prefix provide some differentiation.

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 on when to use this versus kiwi_case_list_attachments, kiwi_plan_list_attachments, or kiwi_run_list_attachments. The description simply states what it does without recommending usage context or exclusions.

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