generate_mock_data

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

With no annotations, the description carries the behavioral burden. It does disclose the kinds of data produced, configurability of count/locale, and notes that credit cards are fake. However, it does not state the output format (e.g., single value vs. array), how 'types' changes record shape, or whether results are deterministic.

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?

Two tight sentences with no filler. The action and data-type list are front-loaded, and the second sentence summarizes the configuration options. Every phrase contributes to understanding.

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?

There is no output schema, so the description should explain what the tool returns. It does not clarify whether a single item or an array is returned, how count interacts with single vs. mixed-type generation, or what happens if both 'type' and 'types' are supplied. This is a meaningful gap for correct invocation.

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 100%, so the schema already documents all parameters. The description adds a human-readable list of data types and mentions count/locale, but does not add operational detail beyond what the schema provides.

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 states a specific action ('Generate realistic mock data') and names the exact resource categories: names, emails, addresses, dates, UUIDs, phone numbers, company names, credit cards, and IP addresses. This clearly distinguishes it from sibling tools like generate_tests or generate_api_mock.

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 implies the obvious use case—generating mock/test data—but does not explicitly explain when to prefer this tool over siblings or when not to use it. There are no exclusions or alternative routing, so the agent must infer usage from the tool name and data-type list.

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