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

Annotations already declare this is a safe, read-only, idempotent operation. The description adds meaningful behavioral context by detailing the returned coverage/score data, per-citation fields, duplicate handling, submission capability, and the default ordering. It does not discuss pagination or error behavior, but it goes well 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?

The description is front-loaded and every clause contributes useful return-value detail, which is important because no output schema exists. It is dense and could be easier to scan with structure, but it is not padded or redundant.

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 that there is no output schema, the description thoroughly covers what the report contains and how the citations are ordered. With all three parameters fully documented in the schema and safety covered by annotations, an agent has enough information to call this tool 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 100%, so the schema already explains limit, filter, and report_id. The description adds no parameter-level meaning beyond what the schema provides. It does mention default ordering, but not how the filter or limit parameters affect results.

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 uses a specific verb, 'Read', and a specific resource, 'Citation Tracker report', then states the report's scope: where the business is listed, missing, or has wrong NAP data. This clearly distinguishes the tool from the sibling report-listing tool and makes the purpose unambiguous.

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?

Usage is implied by the report-reading framing and by the schema note that report_id comes from list_citation_tracker_reports. However, the description itself does not explicitly say to call the list tool first or explain when to choose this tool over alternatives. The guidance is adequate but not fully explicit.

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