list_payees

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

No annotations provided, but description explains default exclude list behavior and references FIELDS.md. It implies a read-only, list operation, which is adequately transparent for this tool.

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?

Concise, well-structured with Args section. Slightly detailed on exclude_fields but necessary. Front-loads main action. No wasted sentences.

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 output schema exists (not shown), return values are covered. Covers purpose, parameters, and usage. Lacks mention of pagination but acceptable for a list tool with unspecified volume.

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?

With 0% schema coverage, description compensates well: explains plan_id usage and exclude_fields default/override semantics, adding meaning beyond the basic type info.

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 'List all payees in a plan' with a specific verb and resource. It distinguishes from sibling tools like get_payee (single) and list_payee_locations (related entity).

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 clear guidance: use list_plans to find plan_id, explains exclude_fields default and override behavior. Does not explicitly state when not to use, but context is sufficient for an agent.

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