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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the agent knows this is a safe, repeatable local read. The description adds that the payload is 'facts and evidence' for a page, which is mild extra context, but says nothing about auth, scoping, or limits beyond the annotations.

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 with no filler or redundancy. It is efficient, though its brevity is partly under-specification rather than disciplined compression.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. But with three required parameters at 0% schema coverage and no usage routing among dozens of siblings, the description leaves real gaps for an agent trying to invoke it correctly.

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 0% across three required parameters (id, marketId, brandSlug), so the description carries the full burden. It only loosely implies that 'page' maps to id and 'market' maps to marketId, and never mentions brandSlug or the required format constraints (uuid, slug). Most parameter meaning is missing.

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 verb (Read) and a resource (a cited page's facts and evidence in a market), so the purpose is inferable. However it does not differentiate this tool from close siblings like parse_evidence, parse_dashboard_finding, or parse_dashboard_insight, which plausibly return similar 'facts and evidence' content. Adequate but vague about what makes a 'page' distinct.

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 when-to-use, when-not-to-use, or alternative-tool guidance. With ~50 sibling parse_* tools, an agent gets no help deciding between parse_dashboard_page and parse_evidence or parse_dashboard_finding. The word 'cited' hints at a prerequisite (something must have been cited first) but it is not stated.

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