getPayeeLocationById

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 says 'Returns a single payee location' and discloses nothing about error behavior, authentication, read-only status, or edge cases like 'last-used'/'default' plan handling beyond the schema.

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?

A single six-word sentence with no filler or repetition. It is appropriately short for a simple retrieval tool, though it could have added sibling differentiation without much cost.

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?

With an output schema present and full schema parameter coverage, the description is mostly sufficient for this low-complexity getter. However, it lacks any usage guidance or clarification of how it differs from sibling list tools, leaving a small but real gap.

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% and both plan_id and payee_location_id are already described clearly in the schema. The description adds no parameter-level meaning, so the baseline of 3 applies.

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?

States the specific verb 'Returns' and the resource 'payee location' unambiguously, and the singular 'single' and 'byId' help differentiate it from sibling list tools like getPayeeLocations and getPayeeLocationsByPayee. It is clear, though it does not explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus the closely related getPayeeLocations or getPayeeLocationsByPayee. The agent must infer entirely from the name and schema that this is for fetching one specific location by ID.

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