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

Annotations already declare readOnlyHint=true, so the safety profile is covered. Because there is no output schema, the description's enumeration of what comes back (level, term, dates, fee, status, auto-renewal, sub-members, payments) meaningfully adds behavioral context about response content.

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 compact segments, with the action and target front-loaded before the field list. The field enumeration is long but earns its place as a proxy for the absent output schema.

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 single-parameter read tool, the description covers what is fetched and what the response contains, and the annotations cover the safety profile. Nothing critical is missing, though error behavior for a nonexistent membership_id is unspecified.

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?

There is a single required parameter at 100% schema description coverage, so the schema already documents membership_id fully. The description only restates it via the REST path (/memberships/{membershipId}), adding no new semantics, which matches the baseline 3 when the schema does the heavy lifting.

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 ('Fetch one membership') and enumerates the returned fields, so an agent knows exactly what it retrieves. The singular 'one' implicitly separates it from neon_list_account_memberships, though no sibling is named explicitly.

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?

Usage is only implied: the required membership_id and the 'one membership' framing make the single-record lookup case obvious, but the description never states when to prefer this over neon_list_account_memberships or what happens with an invalid/missing id.

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