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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is known. The description adds nothing beyond that: it does not say whether attaching is reversible, whether it provisions a new branch/database or links an existing one, whether it consumes quota, or what side effects occur on the target project — all relevant for a non-idempotent mutation.

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?

It is a single short sentence with no filler and the key concept is front-loaded. Brevity here is under-specification rather than tight writing — the sentence is efficient but omits information the agent genuinely needs.

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 mutation tool with no output schema and no annotations covering anything beyond safety, the description should explain what attach produces and how the caller observes success. Instead it leaves the attach target, side effects, and expected result entirely undocumented, which is inadequate for this complexity level.

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 a single parameter at 100% schema description coverage, the schema already carries the semantics (project_id or the session fallback from use_project). The description adds no additional meaning about the parameter, so the baseline of 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?

The description names a specific verb and resource ("Attach" a "Neon Postgres database"), which is more informative than the bare name. However, it never states what the database is being attached to (a project, per the schema) or how this differs from the sibling detach_database, so an agent must infer the object relationship.

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?

There is no when-to-use guidance at all: no mention of prerequisites (an existing project, a Neon provider setup), no indication of when to call detach_database instead, and no note on how this interacts with use_project-based sessions. The agent must derive usage from the parameter schema alone.

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