get_opportunity

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

Describes the tool as a fetch operation, implying read-only behavior. However, since no annotations are present, the description could explicitly state that it does not modify data.

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 that immediately convey purpose and key usage notes. No unnecessary information.

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?

Covers the tool's function, key parameters, and alternatives. Lacks details on error handling or return format, but for a simple fetch, it is sufficient.

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?

Adds usage context beyond the schema, such as the embed parameter example ('tags,fields'). The schema already describes embed, but the description enhances its utility.

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?

Clearly states it fetches a single opportunity by numeric id and distinguishes from sibling 'get_opportunities' which handles batch fetches.

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?

Explicitly provides guidance on using the 'embed' parameter for efficient data retrieval and recommends using 'get_opportunities' for batch operations.

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