get_opportunity

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

Annotations already indicate readOnlyHint and destructiveHint. The description adds value by listing typical return fields (value, milestone, owner, party) and the embed option. It does not mention error handling or missing records, but with annotations present, this is acceptable.

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?

Three sentences that are front-loaded with the core purpose, followed by usage tips and alternative tool. No redundant 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?

Despite no output schema, the description outlines return fields sufficiently for a simple fetch tool. It covers the main usage scenarios and directs to the batch alternative, making it complete for the tool's complexity.

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 schema covers 'embed' with a description, but 'id' lacks description. The description explains the embed parameter's purpose and gives an example ('tags,fields'), and clarifies what the full record contains. This compensates for the partial schema coverage.

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 ('Fetch a single opportunity') and the resource ('by its numeric id'). It distinguishes itself from the sibling tool 'get_opportunities' by specifying single vs batch fetch.

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?

Provides explicit when-to-use: for a single opportunity. Gives an alternative: 'For batch fetches of up to 50 opportunities at once, use get_opportunities instead.' Also advises using the embed parameter for efficiency.

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