filter_parties

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

Discloses that Capsule API does not support ad-hoc sort and provides a workaround. Also explains field name differences. Annotations already indicate read-only and non-destructive, which are consistent.

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?

Clear and front-loaded, but slightly verbose with the workaround example. Still efficient.

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 no output schema, the description adequately covers usage and limitations. The workaround for sorting addresses a common need.

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 high, but description adds significant value by explaining field name mappings (e.g., addedOn vs createdAt) and the conditions array usage for sorting, beyond what schema provides.

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 'Filter parties by structured conditions' and distinguishes from search_parties with concrete examples like 'most recent client', 'parties added this week', 'parties tagged VIP'.

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 this tool instead of search_parties, provides examples, and explains the workaround for sorting using monotonic IDs.

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