add_assertion

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

There are no annotations, so the description carries the full behavioral burden, but it only says 'Add an assertion to validate responses.' It does not disclose that this likely modifies a .jmx test file, whether assertions are appended or replaced, or what happens if the sampler or file is missing. The mutation is implied but side effects are not explained.

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 one short, front-loaded sentence with no filler or repetition. It conveys the essential purpose efficiently, though it could have added slightly more contextual structure without becoming bloated.

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?

The schema fully covers parameters and the operation is relatively simple, but the description lacks behavioral context such as file mutation, side effects, and when to add an assertion in the test-plan workflow. It is minimally viable but has clear gaps around usage and expected behavior.

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 each of the five parameters is already documented in the schema. The description itself adds no extra parameter-level meaning beyond the schema, so the baseline of 3 is appropriate. The value examples in the schema are useful and no compensation from the description is needed.

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 'Add an assertion to validate responses' clearly states the action (adds an assertion) and its purpose (validate responses). It distinguishes this from sibling add_* tools by naming the distinct resource 'assertion', though it does not explicitly compare itself to those siblings.

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 phrase 'to validate responses' implies the tool is used when response validation is needed in a test plan, which gives some contextual direction. However, it does not explicitly state when to use it vs alternatives, when not to use it, or mention prerequisites like having an existing sampler or test file.

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