List NEON sample classes

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

Annotations already cover the read-only, idempotent, non-destructive safety profile. The description adds useful behavioral context beyond those hints: no authentication token is required, and the tool returns descriptions and supports two distinct filtering behaviors. No contradiction with annotations.

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 description is compact and front-loaded, with the core purpose stated first, followed by auth and workflow guidance in short fragments. The final list of neon_get_sample arguments is slightly more than needed for selecting this tool, so it is not perfect.

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 listing tool with rich annotations and an output schema, the description is complete enough: it states the resource, filter modes, auth requirement, and next step. The remaining details, such as pagination defaults, are available in the input 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 coverage is 50%, and the description mostly restates what the schema already says about query and sample_tag. It contributes an example class key but does not explain limit, offset, or pagination behavior, so it does not fully compensate for the undocumented parameters.

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 clearly states a specific verb and resource: 'List NEON's supported sample classes' and gives an example class key. It also distinguishes the two filter modes—text and sample tag—so an agent can tell this apart from list_files, list_releases, and get_sample.

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 gives clear usage context: it is filterable by text or by sample tag, requires no token, and is positioned as the step before neon_get_sample. It does not explicitly state when not to use it or name alternatives, but the workflow guidance is strong enough.

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