test_payload

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

Description implies the tool sends a payload and returns response details, but lacks disclosure of side effects, permissions required, or what constitutes a successful test. Annotations are absent, so description carries full burden but is only moderately transparent.

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?

Front-loaded with purpose, then lists parameters in a consistent format. Slightly lengthy due to many parameters, but each line is informative and necessary.

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?

Covers parameters well but lacks usage context, return value details beyond 'response details', and does not mention prerequisites or warnings. Given complexity and no annotations, more context would improve completeness.

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?

With 0% schema description coverage, description adds substantial value by explaining parameter formats (e.g., headers as key:value pairs separated by |, cookies as key=value separated by ;) and clarifying purposes like WAF bypass technique.

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?

Description clearly states this tool tests a specific SQL injection payload against a target, distinguishing it from sibling tools that perform scans or retrieve results.

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 on when to use this tool versus alternatives, no mention of when not to use, and no differentiation from other scanning tools.

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