Add Opportunity Note

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

The annotations already communicate that this is not read-only and is not idempotent, and the description's 'Add' only restates that mutation is involved. It does not disclose additional behavioral traits such as whether entries are appended, whether existing notes are modified, any permission requirements, or whether this action can be reversed.

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, front-loaded sentence with no wasted words. It states the core action and target resource immediately and remains appropriately sized for a simple tool.

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?

For a simple mutation tool with fully documented parameters, the description is minimally adequate: it names the action and resource, and the schema covers parameter meaning. However, it omits broader context such as output behavior, common use cases, or any relationship to sibling tools, and with no output schema the agent is left without information about what the call returns.

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 input schema fully documents all three parameters. The description adds little semantic value beyond indicating that the tool handles notes or activity logs, which is already reflected in the schema's type field.

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 ('Add') and the resource ('a note or activity log to a pipeline opportunity'), making the tool's function immediately understandable. It is distinguishable from siblings like create_opportunity or update_opportunity_stage, though it does not explicitly name any alternative.

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 the tool is used for adding notes or activity entries to an opportunity, but it gives no explicit when-to-use guidance and does not mention alternatives such as create_task or updating the opportunity. An agent would have to infer appropriate usage from the parameter schema and sibling names.

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