get_bill_payment

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

No annotations are provided, so the description bears the burden. 'Get' clearly implies a read-only operation, but it does not disclose behavior such as what happens when the payment is not found or whether the operation is safe. The description is adequate for a simple GET but lacks explicit safety confirmation.

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 sentence with no wasted words. It is appropriately front-loaded with the verb and resource, making it easy to scan. It could be more informative, but as a concise statement it is highly efficient.

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 the presence of an output schema, return values are covered. The tool is simple, but the description does not explain the dual-parameter requirement or when to use it relative to siblings. The gaps in parameter semantics and usage guidance reduce completeness, but the core purpose is clear enough for a basic 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?

The schema has no descriptions (0% coverage), so the description must clarify parameter meaning. It says 'by ID' but does not mention that both bill_id and payment_id are required, making it ambiguous with two IDs. The parameter names in the schema provide some context, but the description fails to clarify the relationship between them.

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 ('specific bill payment'), clearly distinguishing it from list_bill_payments (which lists all) and create_bill_payment (which creates). The scope is explicit: fetch one entity 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 implies the tool is for retrieving a single bill payment, but it does not explicitly state when to use it versus list_bill_payments or mention that both bill_id and payment_id are required. No alternatives or exclusions are provided, so guidance is minimal but not misleading.

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