databases_set_allow

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

No annotations exist, so the description carries the burden and does disclose the key traits: this is a full replacement (not a merge) of the existing list, an empty list revokes all access, and it requires the databases:write scope. Missing only propagation timing and confirmation of what is 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?

Three short sentences, front-loaded with the verb and resource, then the edge case, then the auth scope. Every clause earns its place and nothing is padded.

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 two-param mutation with a fully documented schema and no output schema, the description covers the essential facts an agent needs: replacement semantics, the empty-list behavior, and the required scope. It stops short of describing the destroy/overwrite risk explicitly or the response shape.

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 both params documented ('pg-<n>' id source and 'IP addresses or CIDRs'), so the baseline is 3. The description's 'who may connect' adds a small amount of meaning to `allow` but nothing beyond the schema on `id` or value formatting.

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?

A specific verb ('Replace') plus resource ('a cluster's allow list') with a parenthetical clarifying the semantics ('who may connect'). This is clearly distinct from the other databases_* siblings (list/get/create/delete), which do not touch the allow list at all.

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?

The purpose implies when to call it, and 'An empty list closes it' gives a concrete usage edge case. However, there is no explicit routing guidance — nothing says to call databases_get first to inspect the current list, or what to do instead when modifying individual entries.

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