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 the upstream API shape (GET /properties/{name}) and the cross-tool dependency on returned ids. It does not discuss pagination or ordering, which keeps it from 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?

Front-loaded with the core purpose, followed by the category list and endpoint. The long comma-separated enumeration is dense but every item maps to an enum value, so little is wasted.

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 single-param read-only lookup with no output schema, the description tells the agent what it returns (ids) and why it matters. Nothing critical is missing, though return shape/pagination is unstated.

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 coverage is 100% with an enum, so the schema already carries most semantics (baseline 3). The description adds value by glossing the categories and flagging that systemTimezones feeds neon_create_activity, which the schema does not convey.

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 ('organization's lookup lists') and immediately characterizes the return as the ids other tools need. The enumeration of list categories makes it unmistakable against siblings like neon_list_accounts or neon_list_campaigns.

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?

Frames usage as supplying ids that other tools require, and explicitly ties systemTimezones to neon_create_activity. It stops short of stating when not to use it or naming a competing alternative, but the use context is clear.

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