get_payment

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

No annotations provided, so the description carries full burden of behavioral disclosure. Fails to specify error behavior (e.g., invalid ID), authentication requirements, rate limits, or what constitutes 'detailed information'. Only implies read-only access through the verb 'Get'.

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?

Single efficient sentence with zero redundancy. Information is front-loaded and appropriately sized for the tool's simplicity; every word earns its place.

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?

Adequate for a simple retrieval tool with complete parameter schema. Lacks description of return values and error scenarios (compounded by missing output schema and annotations), but meets minimum viable standards for a single-parameter lookup operation.

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 coverage is 100% with the 'id' parameter fully documented as 'The payment ID'. The description reinforces this with 'by its ID' but adds no additional semantic details, examples, or format constraints beyond what the schema provides. Baseline 3 is appropriate for high schema coverage.

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 specific action (Get) and resource (payment), and clarifies scope (single by ID). Implicitly distinguishes from list_payments by specifying 'single' and 'by its ID', though it doesn't explicitly name the sibling alternative.

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?

Lacks explicit when-to-use guidance; only implies an ID is required via 'by its ID'. Does not mention list_payments as the alternative when the payment ID is unknown, nor does it state prerequisites or exclusions.

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