Prepare Attachment Download

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

The annotations already mark this as read-only and idempotent, so the description adds valuable non-obvious behavior: the returned URL is one-time and short-lived, must be GET before expires_at without an Allure bearer token, and preparation should be repeated if the URL expires or was already retrieved. This is exactly the kind of behavioral context an agent needs.

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?

Three compact sentences carry the full workflow: the action, the prerequisite call sites, and the URL expiry/recovery behavior. Every sentence contributes essential information with no redundancy.

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?

Given the complete schema, the presence of an output schema, and annotations that establish safety, the description covers everything else needed for correct invocation: prerequisite context, one-time URL handling, auth requirements, and failure recovery. No important call-time behavior is missing.

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%, so the schema fully documents each parameter. The description adds mild context by mentioning 'attachment ID, kind, and owner context,' but it does not materially enrich the parameter semantics beyond the schema.

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 opens with a specific verb and resource: 'Prepare one verified attachment download, then HTTP GET its returned Lucius URL.' It clearly identifies the tool's two-step purpose and differentiates it from upload-focused siblings like add_test_result_attachment and retrieval tools like get_test_result.

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 explicitly states when to call this tool: 'Call this after get_test_result or get_test_case_details provides an attachment ID, kind, and owner context.' It also advises when to re-invoke the tool after expiry or prior retrieval. It does not name alternatives or exclusions, so it falls just short of a 5.

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