filter_parties

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds beyond: discloses Capsule's lack of ad-hoc sort and explains monotonic ID workaround. Does not contradict annotations. Extra context about behavior (sort limitation) earns a 4.

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?

Description is a single paragraph but front-loads purpose and usage. While lengthy due to detailed condition examples, all information is earned and not redundant. Structure is clear and easy to scan.

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 purpose, usage, parameter details, and API limitations. Missing output shape (no output schema), but the tool name and context imply it returns parties. Given 4 parameters and nested objects, description is fairly complete. Could mention return type or pagination handling.

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 has 50% description coverage. Description significantly enhances the conditions parameter: explains field name differences, provides common values, links to full list, and explains operator/value semantics. For other parameters (embed, page, perPage), description adds no extra meaning, but the most complex parameter is well-covered.

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?

Description clearly states 'Filter parties by structured conditions' and explicitly distinguishes from sibling 'search_parties' by specifying when to use this tool. Verb+resource+scope is specific and unambiguous.

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 guidance with examples ('most recent client', 'parties added this week') and explains when not to use alternatives. Also addresses API limitation (no ad-hoc sort) with a workaround, fulfilling both positive and negative usage context.

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