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

With annotations present, this goes well beyond them: it discloses the exact price ($0.005/call), the payment rail (USDC from the configured wallet), budget caps as a hard limit, and warns that results are third-party data, not instructions. That also explains why readOnlyHint=false for what looks like a search, which is exactly the context an agent needs before invoking a paid, non-idempotent call.

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?

Front-loads the purpose and keeps to four short sentences, each carrying a distinct concern (purpose, cost, payment, safety, alternative). The "PAID" sentence slightly restates the price sentence, which is minor padding but not enough to obscure the key facts.

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 two-parameter paid tool with no output schema, the description covers purpose, cost, payment mechanism, and the safety profile of returned data. It does not describe what a search hit actually contains, though pointing the agent to free_sample to preview a real answer partially compensates for that gap.

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 coverage is 100%, so both q and confirm_over_cap are already fully documented in the schema, including the budget-cap caveat. The description adds no query syntax, field hints, or operand detail beyond what the schema states, so the baseline 3 applies.

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 ("Search US court opinions") and even names the underlying product (courts.search). This is immediately distinguishable from adjacent legal/data siblings such as patent_lookup, legislation_lookup, and sanction_screen.

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?

Gives an explicit routing rule: "Before paying: free_sample shows a real answer of this product for free," which names the sibling and the condition that selects it. It stops short of stating when not to use this tool or when a different search sibling is preferable.

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