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

With only destructiveHint=true available, the description carries meaningful extra context: PATCH/partial-update behavior, the type-must-match constraint that will cause a failure if violated, and the exclusion of addresses. It doesn't cover permissions, error behavior, or which values are irreversible, so it isn't exhaustive.

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?

Four short sentences, all front-loaded and information-dense: field list first, then update semantics, then the constraint, then the exclusion and API endpoint. Nothing is padding, though the trailing "Neon: PATCH /accounts/{id}" is the weakest element.

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 12-parameter mutation tool with no output schema and thin annotations, the definition covers the essentials an agent needs: what can change, that it is a partial update, and the type precondition. Missing error/auth context keeps it from a 5.

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 the schema already documents all 12 parameters, including the enum on type and the field mappings. The description's field list is a helpful summary but adds no syntax or format detail beyond the schema, so the 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 (Change) and resource (account) plus an explicit list of the mutable fields (name, email, job title, company name, opt-out flags). The scoping line "Addresses are not edited here" further sharpens what the tool does and does not touch.

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 real preconditions: partial-update semantics ("only the fields you pass are changed"), the requirement that type must match the account, and a pointer to neon_get_account to check it. It also excludes addresses. It stops short of an explicit when-to-use-this-vs-alternative statement, but the guidance is concrete.

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