add_size_assertion

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

With no annotations, the description carries the behavioral disclosure burden. It states the primary effect—adding a Size Assertion and comparing byte size—but does not mention side effects, validation behavior, or what happens if the parent element is invalid. Acceptable for a simple add operation, but minimal.

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?

A single sentence, front-loaded with the action and target, with zero filler. It is efficiently structured and easy to parse.

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 6 parameters, no output schema, and no annotations, one sentence is not enough. It lacks explanation of required IDs, operator semantics, and testField options, and provides no guidance among the many sibling add_* tools.

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 only 17%, so the description must compensate. It adds useful meaning for parentId ('under an HTTP sampler'), testField ('response field'), and size ('byte size'), but leaves planId, operator, and name semantics unexplained.

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 uses a specific verb ('Add'), names the exact resource ('Size Assertion'), and states the precise purpose: comparing a response field's byte size against a threshold. This clearly distinguishes it from sibling assertion tools like add_json_assertion, add_duration_assertion, and add_response_assertion.

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?

It gives placement context by saying the assertion goes 'under an HTTP sampler', which is useful. However, it does not say when to choose a size assertion over the other assertion tools, nor mention any exclusions or prerequisites.

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