get_opportunity

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

No annotations are provided, so the description carries the full burden. It discloses the payment fee, payment mechanism (USDC on Base), error handling (never charged for an error), and the key requirement, all of which are critical behavioral traits.

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 dense but every sentence adds value: payment, output fields, key behavior, and error safety. It is well-structured with key info upfront.

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?

Despite no output schema, the description enumerates all returned fields (freqScore, intensityScore, wtpScore, etc.). It also covers cost, key requirement, and the no-charge-on-error behavior, making the tool fully understandable for a single-opportunity lookup.

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% with descriptions for both id and slug, so the baseline is 3. The description repeats the 'exactly one' constraint but adds no new parameter syntax, format, or examples.

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 it returns one FULL opportunity card by id or slug, listing specific output components. This distinguishes it from siblings like get_opportunities (plural) and get_trending_opportunities.

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?

Provides clear context: exactly one of id or slug must be supplied, and a live call requires EVM_PRIVATE_KEY; without it, the call returns 402 price terms. However, it does not explicitly compare to alternative tools or state when-not-to-use.

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