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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: results are ordered newest first, the auth prerequisite (Cotlet API key with access to this app), and the profile section the data maps to. Pagination behavior is still undisclosed, keeping it short of a 5.

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 opening two sentences are near-duplicates: 'Payments from the customer profile (Activity > Payments), newest first' is immediately re-stated as 'Returns the payments listed under Activity > Payments on the customer profile, newest first.' The 'Momence:' prefix also echoes the title. Useful content, but roughly a third of the text is redundant.

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 no output schema, the description must carry return-value information, and it does at a basic level: payment records, newest first, with an ID consumable by momence_refund_payment. Combined with the disclosed auth requirement and the full schema coverage, an agent has what it needs to call this correctly; only pagination/volume limits are missing.

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 100% - customer_id documents its own source (search_customers) and since documents its date filter - so the baseline is 3. The description adds nothing about parameter syntax or defaults, and its only ID reference (payment_id) is an output field, not an input.

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?

It states a specific verb+resource (list payments for a customer) and pins the location they come from (Activity > Payments on the customer profile). That is enough for an agent to tell it apart from momence_get_customer, momence_search_customers, and momence_refund_payment, though it never explicitly contrasts itself with any of them.

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?

There is no when-to-use / when-not-to-use guidance and no named alternative for retrieving payment history. The one directive present ('Use payment_id in refund_payment') describes how the output feeds a later tool, not when to select this tool over another.

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