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 value by disclosing what the read returns (level, term, dates, fee, status, auto-renewal, sub-members, payments) and the underlying REST endpoint, which matters since there is no output schema.

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 with zero waste: the action and returned fields are front-loaded, and the API path is appended as compact orientation. Nothing is padding.

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 correctly compensates by enumerating returned fields, and one required param at full schema coverage needs no more. Minor omission: no mention of behavior when the id is invalid/not found, but the essentials for a correct call 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% and the single membership_id parameter is documented, so the schema does the heavy lifting. The description reinforces it via the {membershipId} path but adds no format or sourcing detail beyond that; baseline 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?

States a specific verb and resource ('Fetch one membership') and enumerates the payload surface (level, term, dates, fee, status, auto-renewal, sub-members, payments). The singular 'one membership' plus the explicit GET /memberships/{membershipId} path cleanly distinguishes it from the plural sibling neon_list_account_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?

Usage is only implied: fetching a single membership by id versus the list siblings. There is no explicit 'use this when...' or exclusion statement, so an agent must infer the choice from the singular phrasing.

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