generate_test_data

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

No annotations are provided, so the description carries the load, and it does disclose real behavioral distinctions: output is raw values rather than cases with expected outcomes, property mode emits boundary + random + invalid values, and random mode is seeded. It stops short of stating whether generation has any side effects or determinism guarantees beyond 'seeded', which keeps it from a 5.

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?

Three sentences, each doing distinct work: what it produces, per-strategy behavior, and the sibling redirect. The core identity and the exclusion are front-loaded with no filler.

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?

An output schema exists, so return values need not be explained. Given one required input with two discriminated variants, the description covers both modes and the alternative tool, leaving nothing an agent needs before calling it.

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?

Reported schema description coverage is 0% at the top level, so the description must explain the input shape, and it does by describing the two strategy modes and what each produces. Field-level details (constraints, count cap, include_invalid) are left to the nested schema, which documents them 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?

States a specific verb and resource ('Generate raw test data (values)') and immediately contrasts it with what it is not ('not technique-driven test cases'). It names the sibling generate_test_cases, so an agent can separate the two without opening either schema.

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?

Gives explicit routing: strategy='random' for N rows across multiple fields, strategy='property' for boundary/random/invalid values on a single typed field, and 'For classic techniques with expected outcomes, use generate_test_cases.' Both the when and the when-not/alternative are stated.

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