get_opportunities

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

With no annotations, the description carries the burden of behavioral disclosure. The verb 'Get' implies a read-only operation, and 'from sales pipelines' scopes the data source. However, it does not mention optional behavior when filters are omitted, pagination, or response format, which are minor gaps for a simple read 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 a single sentence of six words, immediately front-loading the purpose. It is concise with no filler, earning a top score for efficiency.

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 read tool with two optional, well-documented filters and no output schema, the description adequately conveys what the tool returns ('deals/opportunities') and their source. It does not explain return structure or pagination, but these are not critical for this level of 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?

Schema description coverage is 100%, with both parameters ('stageId', 'pipelineId') described as filters. The tool description does not add extra meaning beyond the schema, but the baseline of 3 is appropriate since the schema already documents the parameters sufficiently.

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 verb 'Get' and the resource 'deals/opportunities' from 'sales pipelines', distinguishing it from sibling tools like get_contacts (contacts) and create_opportunity (create vs. get). It precisely conveys the tool's function.

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 usage for retrieving opportunities, but does not explicitly state when to use it versus alternatives like create_opportunity or get_contacts. There is no mention of exclusions or prerequisites, leaving context to be inferred.

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