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

Annotations only declare readOnlyHint=true, so the description carries most of the behavioral burden; it does disclose the shape of the returned history (including status values like SUCCEEDED/FAILED) and the underlying Neon endpoint, which is valuable given there is no output schema. It does not discuss pagination behavior beyond what the schema already documents.

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, no filler. The field inventory comes first and the endpoint reference is tucked at the end, so the agent gets the essential information immediately.

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, 7-parameter list tool with full schema coverage, the description is nearly complete: it explains the resource, the filterable modes, and the returned fields, compensating for the absent output schema. Pagination is handled by the schema, so only the lack of explicit sibling routing holds it below 5.

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 every parameter is already documented in the schema, including both enum-typed sort parameters. The description's mention of active/primary-active filtering maps directly onto is_active and primary_active_membership without adding format or syntax detail, so the baseline of 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?

The description states a specific verb and resource ('List one account's membership history') and enumerates the returned dimensions (level, term, dates, fee, status, auto-renewal). This clearly distinguishes it from the singular neon_get_membership and from neon_list_membership_levels, which lists level definitions rather than an account's memberships.

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?

The description hints at usage by mentioning the 'filter to active or the primary active membership' options, which maps to two of the filter parameters, but it never states when to choose this tool over siblings like neon_get_membership or neon_list_accounts. Usage is implied rather than specified.

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