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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavioral context beyond them — responses are simulated, grounded in US Census and World Bank microdata, and returned with an honest back-tested calibration score. That tells an agent outputs are estimates rather than real respondent data, which is the key caveat. The trailing truncation prevents 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?

The opening sentence is duplicated verbatim and the text terminates mid-word ('opini'), wasting roughly half the description. The core claim is front-loaded, but the repetition and truncation signal sloppy construction.

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?

For an open-world tool with a free-form nested input and no output schema, the description should explain the expected input shape and roughly what the response distribution contains. It hints at a calibration score but leaves the caller unable to construct a valid request.

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 coverage is nominally 100%, but the single `input` object's description is only a URL pointer and its nested properties are entirely undefined. The description says 'ask any question' yet never clarifies what fields to populate, so it does not compensate for an effectively empty 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?

States a specific verb and resource: 'Ask any question to a representative synthetic audience and get a simulated response distribution.' The synthetic-panel survey concept is distinctive enough to separate it from siblings like ad_radar or ai_brand_accuracy, though no sibling is named explicitly.

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?

It names intended use cases ('pre-test messaging, concepts, pricing and opini...') but the sentence is cut off mid-word, so the guidance is incomplete. There is no statement of when NOT to use it or which sibling tool covers related needs.

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