list_payments

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

With no annotations provided, the description carries full disclosure burden. It mentions filtering and pagination behaviors but lacks safety profile (read-only status), rate limits, error handling details, or specifics about the Shopmonkey API interaction pattern.

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?

Two concise sentences with no redundancy. However, it could be more informative by front-loading the specific filter types available (by orderId, locationId) rather than the generic 'supports filtering'.

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 4 simple parameters and no output schema, the description meets minimum needs by stating the core operation but fails to compensate for the missing output schema by describing what payment data structure or fields are returned.

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%, so schema descriptions already explain orderId, locationId, limit, and page adequately. The description generically mentions 'filtering' which aligns with the parameters but adds no additional semantic detail, syntax constraints, or cross-parameter dependencies beyond the schema.

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 (List) and resource (payments from Shopmonkey), and distinguishes from sibling get_payment (single retrieval) implicitly by describing plural listing. However, it does not clarify how payment listing relates to list_orders or when to prefer get_payment for specific lookups.

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?

Mentions 'filtering' and 'pagination' capabilities but provides no explicit guidance on when to use this versus get_payment for specific records, nor does it state prerequisites like requiring a specific orderId or location context.

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