patchTestStepResultAttachment

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

No annotations are present and the description does not disclose any behavioral traits (e.g., side effects, required permissions, rate limits). The external link does not compensate for missing inline context.

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 but under-specifies the tool's functionality. A link alone does not serve as a concise description; it is insufficient for an agent to understand the tool.

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?

With 8 parameters, 7 required, no output schema, and no annotations, the description is completely inadequate. An agent cannot determine input constraints, return format, or operational behavior from a mere link.

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% with descriptive parameter names and schema descriptions, so the baseline is 3. The description adds no additional meaning but the schema already explains each parameter adequately.

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 is a link to an external guide with no indication of what the tool does. It fails to state the purpose or even the verb+resource relationship.

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 usage context or alternatives are provided. The description is absent, offering no guidance on when to use this tool versus sibling tools like deleteTestStepResultAttachment or postTestStepResultAttachments.

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