neon_list_branches

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

No annotations are provided, placing the full burden on the description. The description only states the action without disclosing behavioral traits such as whether the operation is read-only, if it requires authentication (though api_key is optional), pagination behavior, or any side effects. For a list operation, such transparency is minimal.

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 a single sentence with no wasted words. However, it is possibly too terse given the lack of parameter semantics and behavioral details. It is concise but at the expense of completeness.

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?

Given no output schema and low parameter coverage, the description does not explain what the tool returns (e.g., an array of branch objects, pagination info) or any usage caveats. An AI agent would have to infer the output format from the tool name alone.

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?

With 0% schema description coverage, the description does not explain the meaning of the api_key and project_id parameters. It does not mention that api_key is for authentication or that project_id identifies the context. The description adds no value beyond the schema itself.

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 'List all branches in a Neon project' clearly states the specific verb (list), resource (branches), and scope (Neon project). It effectively distinguishes this tool from siblings like neon_create_branch (create) or neon_get_project (get project details).

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 implies when to use this tool (listing branches for a project), but it does not explicitly provide guidance on when not to use it or mention alternative tools for related tasks (e.g., getting project details). The context is clear but lacks exclusions or contextual comparisons.

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