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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds value beyond that: page size cap (100 per page) with a 'pass page to read on' pagination model, and the auth requirement (Cotlet API key with access to this app).

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?

Front-loaded with the resource and contents, then search dimensions, pagination, downstream usage and auth. Every sentence carries information, though the opening enumeration is dense and could be trimmed slightly.

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?

For a read-only list tool with full param coverage and annotations handling the safety profile, the description covers contents, filtering, pagination and auth. No output schema exists, yet the description does not describe return format, which is the one remaining gap.

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%, so the schema already documents page, type, query and per_page. The description restates the searchable fields and page size, matching rather than extending the schema, so baseline 3 applies.

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 a specific verb (list/search) and resource (transactions) and enumerates exactly what the records contain: payments, rebills, refunds, cancellations with customer, product, amount and invoice ID. This clearly distinguishes it from siblings like thrivecart_list_subscriptions or list_affiliates.

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?

Gives explicit search dimensions (customer name, email, order ID, invoice ID, type) and, unusually, routes the agent downstream: use transaction_id in refund_transaction and subscription_id in pause_subscription/cancel_subscription. Lacks an explicit 'when not to use' or alternative list tool, so not a full 5.

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