List Payees

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

No annotations are provided, so the description carries the full burden. It only states 'Lists all payees in a budget', which implies a read-only operation but does not disclose any other behavioral traits such as pagination, authentication needs, or rate limits. For a simple list tool this is minimally adequate.

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 extremely concise with two sentences, both front-loaded and adding value. Every sentence earns its place without any unnecessary words.

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?

The tool has no output schema, and the description does not explain what information is returned (e.g., payee IDs, names). While the tool name suggests the response includes payee details, the lack of any return format description leaves agents to infer, which is adequate but not comprehensive.

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 input schema has one parameter with 100% description coverage, fully documenting its optional nature and default value. The description adds no additional meaning about the parameter beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 'Lists all payees in a budget' which is a specific verb and resource. It also provides a use case for finding payee IDs. However, it does not differentiate from sibling list tools such as list_accounts or list_categories, which are also present on the same server.

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?

The description includes a usage hint ('Useful for finding payee IDs when creating transactions'), which implies when to use the tool. However, it lacks explicit guidance on when not to use it or alternatives that might be better suited for other scenarios.

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