get_opportunity_details

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

With no annotations provided, the description must disclose behavioral traits. It mentions 'Free' (no cost) and lists returned data types, but does not state whether the tool is read-only, has side effects, or requires authentication. The term 'Get' implies read-only, but it's not explicit.

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 a single sentence that conveys all essential information without redundancy. It is front-loaded with the main action and details, making it easy for an agent to quickly grasp the purpose.

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?

The description mentions the types of information returned ('endpoint, pricing, commission, params'), but without an output schema, it does not describe the structure or format of the response. For a tool that returns multiple data points, more detail on the return value would improve completeness. Additionally, no usage guidance is given.

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?

Both parameters are documented in the schema (100% coverage), and the description adds context beyond the schema: it specifies the source for vendor_id ('from list_affiliate_programs') and gives an example ('coinopai'), and clarifies that product_id is optional. This helps the agent understand where to get the input values.

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 action ('Get full details'), the resource ('a vendor and optionally a specific product'), and what's included ('endpoint, pricing, commission, params'). It distinguishes itself from sibling tools by specifying it provides comprehensive details for a single vendor/product.

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 lacks any guidance on when to use this tool versus alternatives. It does not mention when not to use it or compare it to siblings like 'search_opportunities' or 'list_affiliate_programs'. Only the word 'Free' hints at safety, but no explicit direction.

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