Export records in bulk

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral detail beyond the schema by specifying that records are returned as a single JSON or CSV payload and that nested fields are flattened in CSV. This helps the agent predict output shape and format-specific behavior.

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 three sentences with no filler. It front-loads the core purpose, immediately gives the usage context, and ends with a necessary format behavior. Every sentence earns its place.

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 the rich input schema, output schema presence, and annotations, the description is complete enough for correct selection and invocation. It covers when to use the tool property, the output format, and the CSV-specific behavior, while parameter details are already fully documented.

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?

All four parameters are fully described in the input schema, so the schema carries the baseline burden. The description adds extra meaning around the format parameter by clarifying that the result is a single payload and by describing CSV flattening of nested fields. This is modest but meaningful value beyond the schema.

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 action: 'Generates a batch of synthetic person records as a single JSON or CSV payload.' It identifies the resource (synthetic person records), the verb (generates), and the output format, making the tool's purpose unambiguous. It also hints at the distinction from single-record generators by framing this as a bulk alternative.

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 explicitly tells the agent when to use this tool: 'Use this instead of repeated single-record calls when producing a dataset or fixture file.' This provides clear context and an implicit exclusion, though it does not name specific sibling tools or state when not to use it beyond the repeated-call scenario.

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