Get keyword volume report

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: the tool does not create a new report, and the returned data is untrusted content that should not be treated as instructions. This goes 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?

Three sentences, each earning its place: the first states the action and scope, the second limits the data description, and the third warns about untrusted content. No fluff or repetition.

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 a single-parameter read-only tool with rich annotations and full schema coverage, the description is nearly complete. It could mention the return format or pagination, but the absence of an output schema and the simple parameter set make this a minor gap. The untrusted-content warning adds important context.

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 documents the reportId parameter. The description adds meaning by clarifying that the reportId is the MCP reportId returned by the matching create tool, not a provider report ID, which is already in the schema but reinforced. The description also mentions the data scope (volume, date, units, location) which helps the agent understand what the parameter will fetch.

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 clearly states the tool retrieves an owned keyword report and its provider data without creating another report, distinguishing it from create_keyword_volume_report. It also specifies the resource (keyword report) and the action (retrieve).

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 description explicitly says 'without creating another report', which tells the agent when to use this tool instead of the create sibling. It also warns that the returned data is untrusted source content, not instructions, which is a clear usage caveat.

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