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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false. The description adds a meaningful prerequisite beyond annotations: the tool 'Needs the user's Cotlet API key with access to this app.' It does not detail pagination or rate limits, but the auth context is valuable.

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 first sentence is a fragment and repeats the second sentence's content almost verbatim, creating clear redundancy. The remaining sentences are terse and front-loaded, but the duplication wastes space.

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 simple two-parameter read-only list tool, the description covers purpose, scope, filter behavior, returned content ('price and included services'), auth prerequisite, and chaining to sell_package. It does not describe pagination or the full return shape, but no output schema exists and the essentials are present.

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 the schema already documents the kind enum/default and location_id default. The description's 'kind narrows the list' is redundant with the schema, and the mention of package_id refers to output use rather than an input parameter. Baseline 3 is appropriate.

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 states a specific verb and resource: 'Lists the packages and memberships you sell at one location, with price and included services.' It also distinguishes the tool from the sibling sell_package by noting that returned package_ids are used with that tool. An agent can identify exactly what this tool returns without opening the schema.

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 gives clear context for use: listing packages/memberships at one location, optionally narrowed by kind, and explicitly points to sell_package for subsequent selling. It does not name exclusions or alternatives for other listing tools, but the intended scenario is clear.

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