get_parties

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

Discloses internal chunking for 11-50 ids, parallel Capsule calls, and merged results. Complements readOnlyHint=true annotation with useful implementation details.

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?

Three sentences, front-loaded purpose, efficient word choice, no redundancy.

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 main use case and internal behavior. No output schema, but description gives reasonable context. Could mention error handling for invalid IDs, but not critical.

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 100%, so baseline 3. Description adds context about chunking behavior for ids and notes result shape is identical regardless of input size, exceeding schema descriptions.

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 'Batch-fetch up to 50 parties by ID.' Distinguishes from siblings like get_party (single) and search_parties (search).

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 advises using this when Claude has several party IDs to avoid N sequential round trips of get_party. Does not state when not to use, but implied.

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