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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds value beyond that by disclosing the return fields (accountId, names, email, userType) and the underlying API mapping (GET /accounts), which matters since no output schema exists. It does not mention rate limits or result caps, keeping it short of a 5.

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?

Three tight sentences: purpose and filters first, return shape second, alternative route third, API mapping last. Nothing is redundant and the most decision-relevant information is front-loaded.

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 a read-only annotation and no output schema, the description carries the return-value burden and does so adequately by listing returned fields, plus it maps to the API endpoint. Pagination defaults are left entirely to the schema, which is acceptable, but a note on result ordering or paging limits would have completed the picture.

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%, so every filter and pagination parameter is already documented in the schema. The description restates the filterable fields (email, first/last name, type) without adding format, matching semantics, or combination behavior, making it a baseline case.

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 (List) and resource (constituent accounts), defines the resource scope as individuals and companies, and enumerates the available filters. It explicitly separates itself from the sibling neon_search for richer queries, so an agent can route correctly without opening either schema.

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?

Gives a clear use condition (simple filtered listing) and names the alternative tool (neon_search) for richer queries. It stops short of stating when-not to use it (e.g. when a single account is needed, neon_get_account) or any prerequisites, so it is clear but not exhaustive.

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