keap_update_opportunity

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

No annotations are provided, so the description fully bears the burden of disclosing behavioral traits. It only states 'update an existing opportunity,' omitting side effects, permission requirements, field constraints, or that it modifies the opportunity in the system. For a mutation tool with 10 parameters, this is insufficient.

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?

At one sentence, it is concise but potentially under-specified. The description efficiently conveys the basic action but could include a brief one-liner about scope (e.g., 'fields listed in input') without sacrificing conciseness. It achieves a bare minimum.

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?

Given the lack of output schema and annotations, and the presence of 10 parameters, the description does not guide the agent on expected return values, error handling, or effective usage. It fails to provide a complete mental model for the tool's operation.

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 description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema's property descriptions, providing no grouping, relationships, or usage tips. It neither detracts nor adds value.

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 'Update an existing opportunity' clearly states the action (update) and resource (opportunity), distinguishing it from sibling tools like create, delete, or get opportunity. However, it does not differentiate from the highly similar sibling keap_update_opportunity_stage, which updates only the stage field, potentially causing confusion.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., keap_update_opportunity_stage for stage-only updates) or prerequisites (e.g., opportunity must exist). The description lacks any when-to-use or when-not-to-use context.

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