generate_boundary_violations

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

No annotations are provided, so the description must fully convey behavioral traits. It only states that it generates invalid payloads, but omits details like whether the operation is stateless, what the output format is, or any constraints on the input schema. This is insufficient for a generative tool.

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 two sentences long and front-loads the core purpose. It is concise, though the second sentence ('Use to answer...') is somewhat informal but still clear. No wasted words.

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 no annotations, no output schema, and only one parameter, the description is incomplete. It does not explain the output format, any prerequisites (e.g., schema must be valid Zod), or limitations. For a tool that generates test data, this missing information reduces 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?

Schema coverage is 100% for the single parameter schema_code, so the description does not need to add much. It merely repeats 'Zod schema code', adding no extra meaning beyond the schema's description. Baseline 3 is appropriate.

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 clearly states the verb 'generate' and the resource 'invalid payloads based on a Zod schema' with the explicit purpose 'for negative testing'. It distinguishes itself from siblings like generate_valid_mock by focusing on invalid payloads.

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 description provides clear guidance on when to use the tool: 'for negative testing' and to answer 'what invalid inputs should I test against this API?'. However, it does not explicitly mention when not to use it or compare with alternatives, though the context of siblings implies distinct use cases.

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