filter_opportunities

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

With no annotations, the description carries full behavioral disclosure burden. It reveals that Capsule's API does not support ad-hoc sort but offers a workaround using date filters and monotonic IDs. Also explains field naming discrepancies between filter and response schemas. Lacks explicit statement about read-only nature, but safe to infer.

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, dense paragraph covering purpose, usage, and behavioral details. While comprehensive, it could be slightly more structured (e.g., breaking into sentences) for easier scanning. However, it is front-loaded and each sentence adds value.

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?

Given the tool's 4 parameters, no output schema, and presence of sibling filtering tools, the description is complete. It addresses filtering mechanics, sorting limitations, field mappings, and even links to external API documentation for more details.

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 description adds significant meaning beyond the schema, such as listing common field names, operator semantics, how to handle null values, and the monotonic ID trick. For a schema with 50% description coverage, this fully compensates and provides practical usage details.

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 purpose: 'Filter opportunities by structured conditions (milestone, value, close date, tags).' It also distinguishes from the sibling tool search_opportunities by specifying use cases like 'last won deal' or 'opportunities closed this month'.

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 instructs when to use this tool over search_opportunities, providing example queries. It also includes guidance on handling sorting limitations with Capsule's monotonic IDs, showing a thorough understanding of usage context.

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