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

The description states 'Read only,' but the annotation declares readOnlyHint=false, which directly contradicts the claimed read-only behavior. Although the description does add useful data-reliability context (J-0001 labels KNOWN / INFERRED / CONFLICTED), the explicit contradiction of the annotation makes this a serious transparency failure.

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 compact sentence front-loads the scoping constraint and the returned data types with zero filler. The dense colon-separated clauses and internal jargon ('Panel B', 'J-0001') slightly reduce readability.

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?

With only two well-documented parameters and no output schema, the description does cover the return contents (survey, forecast, Panel B numbers plus labels). However, it omits format/volume expectations and its read-only claim conflicts with the annotations, leaving the behavioral picture incomplete.

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 both actor_token and matter_id are fully documented in the schema (matter_id even cross-references atlas.enter_demo). The description adds no parameter-level detail, so the baseline of 3 applies.

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 specific resource (the SYNTHETIC survey, forecast and Panel B numbers) and scopes it to 'Practice mode, Consumer Pulse copy only,' which distinguishes it from pulse_inbox, pulse_memo, and pulse_verify_receipt. It lacks an explicit verb (retrieve/read/fetch), so the action is only implied by the tool name.

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 scope condition 'Practice mode, Consumer Pulse copy only' gives a when-to-use signal, but no alternatives are named and there is no statement of when-not-to-use or prerequisites beyond the actor_token requirement. Usage is implied rather than fully guided.

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