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

Annotations already declare readOnlyHint and destructiveHint, but the description adds crucial behavioral context: the tool cannot open checkout, subscribe, or purchase, and it must precede explicit user confirmation. It also discloses automatic-fulfillment expectations and public-source limitations, which go beyond the structural hints and prevent misuse.

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 two sentences, front-loaded with the concrete return payload, and every clause adds value—detailing scope, limitations, and required user confirmation. There is no redundancy or filler.

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 an informational read-only tool with no parameters and no output schema, the description fully covers the return content, boundaries, and expected agent behavior. It leaves no ambiguity about what this tool does or how it should be used in a workflow.

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?

The tool has zero parameters, and the schema is fully covered by the description with no properties. Per the rubric, a baseline of 4 is appropriate when there are no parameters and the description does not need to compensate for missing parameter information.

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 ('Return') and resource ('Medicare Roster Watch offer') and enumerates exactly what is provided: monthly price, NPI scope, delivery, limitations, and paths. It clearly distinguishes this from sibling tools by naming the specific offer and explicitly stating it is informational and read-only.

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 states when to use the tool: to present the offer and require explicit user confirmation before any separate checkout or purchase. It excludes actions like opening checkout, subscribing, or purchasing, which serves as a clear usage boundary. It does not name alternative tools, but the context is sufficient for an agent to decide.

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