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

readOnlyHint=true already tells the agent this is a safe read, so the description's addition is modest. It does add the underlying endpoint (GET /campaigns) and the shape of records returned, but says nothing about pagination, ordering, or whether all campaigns are returned.

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?

One short sentence plus a terse endpoint reference, with the resource named first. Nothing is padded and every fragment carries information.

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 no output schema, the description usefully enumerates the returned fields, which is the main thing an agent needs. It omits any note on result volume or pagination behavior, a minor gap for a list endpoint that takes no arguments.

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?

The schema has zero properties, so there are no parameters to document and the baseline is 4. The parenthetical field list describes response content rather than inputs, which is a small bonus beyond an empty schema.

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 and resource ("List fundraising campaigns") and enumerates the fields returned (id, code, name, status), which is enough to separate it from the singular neon_get_campaign sibling. It stops short of explicitly contrasting itself with that sibling, so it is clear but not maximally differentiated.

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?

Usage is only implied by the verb "List"; there is no statement of when to prefer this over neon_get_campaign or neon_search, and no exclusions or prerequisites. For a zero-parameter list tool the implied reading is unambiguous, but no explicit guidance is provided.

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