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

Annotations already declare readOnly=true, idempotent=true, destructive=false and closed-world, so the safety profile is fully covered. The description adds real value by disclosing the response includes notes and activity history, but says nothing about not-found behavior or the cost/size of that history.

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?

One front-loaded sentence with no filler; the resource and payload are stated immediately. The only blemish is the hedged 'opportunity/deal' phrasing, which slightly blurs the domain term.

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 two-parameter read tool with rich annotations and no output schema, the description is close to sufficient, but it omits the important precondition that an opportunity_id must come from list_opportunities and says nothing about how a missing opportunity is handled.

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 coverage is 100%, so both parameters are documented in the schema and the baseline applies. The description adds nothing about opportunity_id format or how the optional company parameter interacts with the lookup.

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?

States a specific verb ('Get') plus the resource ('pipeline opportunity/deal') and even enumerates the payload ('notes and activity history'). It implicitly contrasts with list_opportunities by scoping to 'a specific' record, but never names that sibling.

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?

Usage is only implied: 'a specific' suggests the agent must already have an ID, which implies list_opportunities to obtain one. There is no explicit when-to-use/when-not or any mention of the alternative tool.

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