emu_generate_cdrs

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses that output is 'realistic synthetic' data and names three analysis scenarios, but it never states whether generated records are persisted (relevant given siblings emu_get_cdr_records, emu_export_cdr_csv, emu_publish_cdr) or merely returned. This is a meaningful transparency gap for a generation tool that appears to feed other tools.

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?

A single front-loaded sentence: verb, resource, and three use cases, no filler. Slight deduction because the trailing use-case list is useful but could have been swapped for a behavioral note about storage/return semantics, which matters more to an agent.

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?

No output schema exists and the description never states the return value format, whether CDRs are stored for later retrieval (needed given emu_get_cdr_records/emu_export_cdr_csv siblings), or whether generation has side effects on state. An agent cannot reliably predict whether this returns records, an ID, or writes to a store, which is material for a generation tool.

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 descriptions cover 100% of the 4 parameters, including defaults and the pattern enum values. The description adds no extra meaning beyond the schema — e.g., it doesn't clarify the relationship between durationMin and durationMax or default bounds. With full schema coverage the baseline of 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?

Clear specific verb+resource: 'Generates realistic synthetic Cisco Call Detail Records (CDRs)' with stated use cases (load testing, abandoned call analysis, CURRI block reporting). Distinguishes from siblings like emu_get_cdr_history (fetch) and emu_export_cdr_csv (export/format) by its generative nature ht, though it doesn't explicitly call out the closest kin emu_seed_fixtures.

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 pattern parameter enumerates use contexts (normal, abandoned, curri-blocked, burst), which implies when it's relevant — abandoned call analysis, CURRI block reporting. But there is no explicit guidance on when to prefer this over emu_seed_fixtures or emu_simulate_call, nor when not to use it. The context is inferable but not directly stated.

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