keap_get_opportunity

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

No annotations are provided, so the description must carry the full burden. It discloses the API endpoint and the optional_properties parameter, but it does not mention error behavior (e.g., 404 not found), default fields returned, authentication needs, or any side effects. This is a significant gap for a retrieval tool.

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 concise and well-organized: a one-line purpose, the API reference, and an Args block. Every line adds value without redundancy or unnecessary detail.

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 tool is a simple retrieval operation with an output schema, so the description does not need to explain return values. However, it is missing guidance on when to use it versus other tools and lacks behavioral details like error handling, making it only partially complete for an agent.

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?

The input schema only provides types and titles, but the description adds meaningful context: opportunity_id is 'the opportunity's unique ID' and optional_properties is a 'comma-separated list of extra fields to include.' This clarifies the purpose and format of both parameters, going beyond what the schema offers.

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 opens with 'Retrieve a single opportunity by ID,' which is a specific verb+resource statement that clearly distinguishes this tool from siblings like keap_list_opportunities. It also provides the exact API endpoint, reinforcing its purpose.

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 implies this tool is for fetching a single opportunity by ID, but it does not explicitly mention when to use it over alternatives (e.g., keap_list_opportunities) or provide any exclusions. The usage context is present but not elaborated.

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