get_payee_locations_by_payee

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

The description only repeats the tool's name without adding behavioral context beyond annotations. Annotations already declare readOnlyHint and destructiveHint, but the description does not disclose pagination, ordering, default behavior, or error conditions. A higher score would require additional behavioral 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?

The description is a single, efficient sentence with no unnecessary words. It front-loads the core purpose without filler, making it easy for an agent to parse quickly.

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?

For a simple read-only tool with well-documented parameters and annotations, the description is minimally adequate. However, it lacks mention of return format, default budget behavior, or potential pagination, which would improve completeness. The output schema is absent, shifting burden to the description.

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 description coverage is 100%, so the baseline is 3. The description does not elaborate on parameters, but the schema already provides adequate descriptions for budgetId and payeeId. No contradiction or extra value added.

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 'Get all locations for a specific payee', which is a specific verb+resource combination. It effectively distinguishes from siblings like 'list_payee_locations' (which likely returns all without filtering) and 'get_payee_location' (singular), making the tool's purpose immediately clear.

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 provides no guidance on when to use this tool versus alternatives. It does not mention 'list_payee_locations' or 'get_payee_location', nor does it explain scenarios where this filtering is appropriate. Agents lack context for selecting the right tool.

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