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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the returned field set and the underlying Neon endpoint, which is modestly useful context, but says nothing about pagination behavior, result limits, or ordering even though two of three parameters are pagination controls.

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?

One front-loaded sentence that names the resource and its returned fields, plus a short endpoint pointer. Nearly zero waste, though the 'Neon: GET /memberships/levels' fragment is mostly protocol trivia for an agent that already has 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?

With no output schema, the description usefully enumerates the fields returned, so the agent knows what it gets back. For a three-parameter, no-required-args list tool this is close to sufficient; the only real gap is that pagination semantics are left entirely to the schema.

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 each of the three parameters is documented in the schema, so the baseline of 3 applies. The description adds no parameter detail of its own – the status filter and paging controls go unmentioned – but nothing is left ambiguous by the schema either.

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 and resource ('List the organization's membership levels') and enumerates the returned fields (id, code, description, rank, type, status), which pins down exactly what a 'level' is. It does not differentiate from the closely-named siblings neon_get_membership or neon_list_account_memberships, so the agent must infer the distinction from names alone.

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?

There is no when-to-use guidance and no mention of alternatives, even though the sibling list contains several membership-related tools (neon_get_membership, neon_list_account_memberships) where the boundary matters. The scope is only implied by the word 'organization's' and the plural resource name.

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