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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds real value the annotations cannot: 'Existing rows keep stale keys until edited' discloses the concrete data consequence of removal. It does not state permission requirements or whether removed field data is recoverable, so it stops short of 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?

Two sentences with zero filler; the replace semantics are front-loaded, and the destructive consequence follows immediately. Every clause earns its place.

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 and full param coverage in the input schema, the description needs only to cover destructive behavior, which it does via the stale-keys note. Minor gaps remain around auth/permissions and whether removed fields affect existing data irreversibly.

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 'slug', 'id', and 'schema' (including 'Full field list; replaces the old one'). The description's 'whole field list' phrasing reinforces the replace semantics but adds no format or syntax 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+resource ('Replace a collection's whole field list') and clarifies the scope is the entire schema, not a per-field edit, which separates it from update_collection_row. It also names get_collection as the read counterpart, giving an agent enough to place it among siblings.

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 parenthetical 'get_collection returns the current one' implies a read-then-replace workflow, which is useful implied guidance. However, there is no explicit when-to-use/when-not, nor a warning about when this is preferable to more targeted row/schema operations.

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