get_opportunities

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

Discloses internal splitting and parallel request handling, and states return includes full record fields. Annotations already indicate read-only and non-destructive; description adds valuable behavioral context without contradiction.

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?

Front-loaded main purpose in first sentence. Each subsequent sentence adds necessary context (internal behavior, return content, alternative). No redundant words.

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?

Covers key aspects: id range, fan-out behavior, return fields, and sibling reference. Lacks details on error handling or pagination, but for a batch fetch by ID this is sufficient given no output schema.

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 baseline is 3. Description repeats splitting logic for 'ids' and gives an example for 'embed' but does not add novel constraints or format details beyond schema.

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?

Clearly states the verb 'batch-fetch', resource 'opportunities', and scope 'up to 50 by id'. Distinguishes from sibling get_opportunity (single id) and filter_opportunities (not by id).

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?

Explicitly tells when to use (batch fetch by id) and when not (single id → use get_opportunity). Also explains internal fan-out behavior for 11-50 ids, aiding usage decisions.

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