postTestStepResultAttachments

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

With no annotations present, the description carries full burden for behavioral disclosure. It adds one specific behavioral detail (identification by order or 'lid'), but omits other critical traits such as idempotency, error handling, permissions, size limits, or response structure. This minimal addition offers limited transparency.

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 extremely short (one sentence plus a link), but it lacks front-loading of essential information. The first sentence is vague and does not immediately convey the tool's purpose. Conciseness is not valuable if it sacrifices clarity and actionability.

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 tool has 7 required parameters, no output schema, and no annotations, the description is woefully incomplete. It fails to explain the tool's purpose, expected request body format, response behavior, or when to use it. The link to external documentation is not sufficient compensation for the missing context.

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?

All 7 parameters have descriptions in the input schema (100% coverage), so the schema already documents parameter meanings. The tool description adds no additional parameter semantics beyond hinting at the 'lid' attribute, which is not a parameter. Baseline score of 3 is appropriate as the description does not reduce ambiguity or provide extra context.

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 does not explicitly state the tool's primary action, such as 'upload' or 'create' attachments. It focuses on how files are identified (by order or 'lid' attribute), leaving the core purpose ambiguous. The tool name suggests posting attachments to a test step result, but the description fails to confirm this, relying on the user to infer from the name.

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 sibling tools like postTestRunAttachments or postTestRecordAttachments. There is no mention of context, prerequisites, or alternatives, leaving the agent without decision criteria.

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