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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds little beyond stating 'Read-only'. It does clarify no checkout or payment obligation is created, which is useful, but given the annotations already cover safety, the description's added value is minimal.

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?

Two concise sentences, zero waste. The primary purpose is front-loaded, and the read-only clarification is efficient.

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 zero-parameter, read-only tool with rich annotations, the description is complete. It lacks return format details, but with no output schema and simple purpose, this is a minor gap. The mention of 'paid' options clarifies the tool's scope.

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?

With zero parameters, the schema is fully covered and the description needs no parameter details. Baseline 4 is appropriate since there is nothing to explain about parameters.

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 lists current paid FindMyPart hunt options and pricing, using a specific verb and resource. It distinguishes itself from siblings by focusing on offers/pricing, though it could be more explicit about how it differs from get_findmypart_capabilities, which might also list options.

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 implies usage for viewing offers before purchasing, and the 'read-only' note hints when not to use it (for actual purchases). However, it doesn't explicitly name alternatives like prepare_part_hunt_checkout for when the user wants to buy, leaving some inference needed.

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