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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds genuinely new behavioral context: results are Gingr-paged via limit+offset and cancelled records are excluded unless explicitly requested. It does not mention rate limits or ordering, which keeps 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?

Two tight sentences front-load the resource and scope, then cover filters and paging with no filler. The trailing 'Gingr: GET /api/v1/get_subscriptions.' is useful provenance but slightly redundant with the tool name.

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 seven-parameter, all-optional read tool with no output schema and read-only annotations already declared, the description covers filtering, paging and the deleted-record toggle adequately. It stops short of noting sort order or the general shape of returned subscription records.

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 all seven parameters with bounds and defaults. The description restates the main filter axes (owner, location, package, billing day) and the paging model without adding syntax or nuance the schema lacks, which is the expected baseline.

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 gives a specific verb and resource ('List recurring subscriptions (membership packages)') and clarifies scope with the available filter dimensions. It implicitly separates itself from the singular sibling gingr_get_subscription, but never names it, so the sibling differentiation is left to inference.

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?

It states that the owner/location/package filters are optional and that cancelled subscriptions appear 'if asked,' which implies the include_deleted behavior. However, it never says when to prefer this list tool over gingr_get_subscription or how it relates to owner lookups, so usage is only implied.

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