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

No annotations are provided, so the description carries the full disclosure burden. 'Get' weakly implies a read, but nothing states whether the call is non-destructive, whether it requires auth, whether quoted prices expire or are guaranteed, or what happens if the results were already unlocked — all meaningful for a quote endpoint.

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?

One sentence, front-loaded with the core action and ending with the scoping constraint. No filler or redundant restatement of the tool name.

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?

There is no output schema and no annotations, so the description is the only source of contract detail; it covers purpose and the input's origin but not the shape of the quote returned or edge cases (expired search, already-unlocked results). Adequate for a simple one-parameter read, but with clear gaps.

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 a single parameter at 0% schema description coverage, the description must compensate. It does clarify that search_id refers to an existing PaidHandshake search, but gives no format, no source (where the id comes from), and no failure behavior for an invalid id, so compensation is partial.

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?

States a specific verb and resource (get prices for unlocking additional ranked results) plus the scope constraint (an existing PaidHandshake search). An agent can tell this is a pricing lookup rather than the purchase itself, but no sibling is named or contrasted.

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?

Phrase 'from an existing PaidHandshake search' implies the prerequisite that a search must already exist and supplies its id, which is useful routing context. However, it never says when to call this versus create_checkout (the natural follow-on purchase step) or any other sibling, so usage is only implied.

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