toast_get_payment

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'Get detailed information'. It does not reveal what fields are returned, whether restaurantGuid affects behavior, whether permissions are required, or any rate-limit or side-effect considerations.

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 short and front-loaded, but it is under-specified: 'detailed information' is vague and does not compactly convey the important scoping or parameter details. It is concise in length but not optimally structured for agent decision-making.

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 no output schema, no annotations, and 0% parameter description coverage, this description is not sufficient for an agent to confidently call the tool. It fails to clarify what 'detailed information' includes, what paymentGuid format is expected, or when restaurantGuid is required.

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 0% and both parameter descriptions are empty. The tool description does not mention paymentGuid or restaurantGuid at all, so it adds no meaning beyond the raw parameter names.

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 uses a specific verb ('Get') and resource ('detailed information about a specific payment'), making the basic purpose clear. However, it does not distinguish this from payment-related siblings like toast_get_payment_summary, toast_get_check_payments, or toast_get_payment_type_report.

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 about when to use this tool versus alternatives, when the optional restaurantGuid is needed, or what prerequisites exist. The description simply states what it does without any usage context or exclusions.

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