Get Payee Location

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

The description explicitly states 'Read-only', which aligns with and reinforces the annotations (readOnlyHint=true, destructiveHint=false). It adds context about the required input source (from list_payee_locations), which is useful behavioral information beyond the annotations.

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 that front-loads the core function, includes the return fields, and notes the read-only nature. Every word earns its place with 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?

For a simple single-record retrieval tool with an output schema present, the description is complete. It covers the input requirement, the read-only nature, and the return fields. The only minor gap is not describing error behavior (e.g., what happens if the ID doesn't exist), but that's not critical for a read-only getter.

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 schema already documents both parameters. The description adds minimal parameter meaning beyond the schema, but it does clarify that payeeLocationId is the primary identifier and that budgetId is optional (uses default). This is baseline 3 territory.

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 the tool's function: 'Get one payee location record by its ID' with the specific fields (payee, latitude, longitude). It distinguishes itself from sibling tools like list_payee_locations and get_payee_locations_by_payee by specifying it retrieves a single record by ID.

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 explicitly states it requires a payee-location ID from list_payee_locations, providing clear context on when to use this tool. It doesn't explicitly exclude alternatives, but the single-record-by-ID scope is clear enough to differentiate from list operations.

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