disparity_panel

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

Annotations already declare readOnlyHint=true, so no safety-warning burden falls on the description. The description adds the useful behavioral fact that the output is synthetic, not real data. It does not describe generation mechanics, caching behavior around as_handle, or any side effects, but the schema and annotations cover much of that ground. No contradiction with annotations exists.

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 extremely concise, with no filler words, and front-loads the core fact that this is a synthetic panel. It is appropriately sized for a simple data-generation tool, though the noun-phrase construction instead of a full instruction prevents a perfect score.

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 presence of a full output schema, 100% parameter documentation, and read-only annotations, the minimal description is partially sufficient. However, with 8 parameters, 0 required, and many related siblings, an agent still lacks context about what the panel represents, when to call it, or how its output feeds downstream tools. The core idea is present, but meaningful gaps remain.

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%, and each parameter, especially `detail`, carries a rich explanation including token estimates and use cases. The tool description itself adds no parameter-level meaning, but the baseline of 3 is appropriate because the schema does the heavy lifting.

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 identifies the resource as a 'synthetic disparity panel' with treatment, mediator, and outcome components, which implies generation of simulated data. However, it lacks an explicit verb like 'generate' or 'simulate,' and does not distinguish itself from the many sibling decomposition and panel-analysis tools. It is more than a tautology but not a precise operational statement.

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?

There is no guidance on when to use this tool versus alternatives such as disparity_decompose or mediation_decompose. The word 'synthetic' hints at usage for testing or demonstration, but no explicit when-to-use, when-not-to-use, or alternative-selection guidance is provided.

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