sx_list_payments

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

The description explicitly states that write operations are permanently prohibited, making the read-only behavior clear. With no annotations present, this disclosure is valuable. However, it omits other behavioral details like pagination or sorting specifics, which are partially implied by parameters but not described.

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 extremely concise, with two sentences. The first states the purpose and resource; the second adds a critical safety note. No redundant information, and the structure is front-loaded and effective.

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 8 parameters, zero schema descriptions, no output schema, and no annotations, the description is woefully incomplete. It does not explain parameter formats, response structure, or usage context, making it inadequate for an agent to correctly construct and interpret a query.

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 0% description coverage for its 8 parameters, and the description provides no explanation of fields, status, date ranges, pagination, or ordering. The agent is left without any semantic guidance beyond parameter titles, making effective use impossible without external knowledge.

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 states the tool queries payment bills (bdi_ex_pay), naming a specific resource and the read-only nature. It clearly differentiates from sibling list tools like sx_list_reimbursements and sx_list_loans by focusing on payment bills.

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 provides no guidance on when to use this tool versus alternative list tools. It does not mention conditions for selection, exclusions, or scenarios where another tool should be preferred, leaving the agent to infer usage context.

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