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

The description asserts 'Read only', but the annotations declare readOnlyHint=false, directly contradicting the stated safety profile. Although it usefully discloses the practice-mode/copy-only scoping, the explicit read-only claim against a non-read-only annotation is a serious inconsistency.

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?

It is a single sentence with the scoping constraints front-loaded, so an agent learns the domain and step before the payload detail. Slightly dense and jargon-heavy, but no sentence is wasted.

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, and the description does describe the returned payload (two conflicting records, the Magistrate question, the copy's standing), which is helpful. But with a contradictory readOnlyHint and no clarity on whether the call changes state, it leaves a material gap for an agent deciding whether the call is safe.

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 parameters (matter_id, actor_token) are documented in the schema itself. The description adds no parameter-level syntax, format, or default information beyond what the schema already provides, 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 names a specific resource and scope: 'Practice mode, Consumer Pulse copy only (Magistrate demo, step 1)' and enumerates the returned content (the two disagreeing records, the fixed Magistrate question, the copy's standing). It is clearly distinct from siblings like atlas.pulse_data or atlas.pulse_memo, though it uses a noun phrase rather than an explicit verb.

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?

'Magistrate demo, step 1' situates the call in a sequence and 'Practice mode, Consumer Pulse copy only' constrains where it applies, which is implied usage guidance. However, it names no alternative tool and gives no explicit when-not-to-use condition, so an agent must infer the routing.

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