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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds the useful detail that results include policies and discounts, and hints at a next_page continuation token that is otherwise only mentioned in the page parameter's schema text. It does not disclose pagination envelope shape, total counts, or limits.

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 sentences, front-loaded with the resource and returned contents, followed by filtering and pagination. Nothing is wasted, though the pagination clause is terse to the point of ambiguity.

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?

Eleven all-optional parameters are fully documented in the schema, and the description summarizes the result contents. Missing: no output schema, and the description's 'next_page' reference is not reconciled with the numeric 'page' parameter, leaving the continuation workflow slightly unclear.

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%, and every filter, sort, and pagination parameter is documented in the schema, so baseline is 3. The description only restates the filter categories already documented and adds no format or behavior details beyond 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?

States a specific verb+resource (list subscription plans, clarified as selling plan groups) and names the payload contents (delivery/billing policies and discounts). It distinguishes itself from recurpay_get_plan by being a listing operation, though it does not explicitly contrast with the similarly named recurpay_list_plan_products.

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?

Filter and pagination usage are implied by 'Filter by plan title, product title/handle and dates' and 'Page with next_page.' There is no explicit guidance on when to choose this over recurpay_get_plan or recurpay_list_plan_products, so usage must be inferred from the sibling names.

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