set_model_denylist

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

Annotations already declare the write, destructive, and non-idempotent profile, so the [WRITE][risk=medium] tag is largely redundant. The description does add real context beyond the annotations: "Replace" discloses full-overwrite semantics (existing entries are discarded) and "deny patterns always win" discloses precedence over the allowlist. It says nothing about validation, persistence, or required permissions.

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?

Terse header plus a one-line Args block is front-loaded and waste-free. The risk tag partially duplicates the annotations, but the size is well matched to a one-parameter tool.

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?

Given a single parameter, no output schema, and annotations covering the safety profile, the description is close to sufficient: it names the resource, the replacement semantics, the precedence rule, and the pattern syntax. It omits interaction with the allowlist tool and any confirmation/permission requirements, which leaves a mild gap.

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 0% and the schema only types the single parameter as an array of strings, so the description must carry the burden. "Shell-glob patterns of forbidden model names" adds the matching syntax (shell-glob) and the meaning of each element, which is exactly what the schema omits.

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 ("Replace the model denylist") plus the scope qualifier that deny patterns take precedence. An agent can distinguish it from the sibling set_model_allowlist by the resource word alone, though no sibling is named explicitly.

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?

No when-to-use or when-not-to-use guidance is given; the agent is not told when to choose this over set_model_allowlist, pin_model_digest, or removal tools. The "deny patterns always win" note hints at precedence relative to the allowlist but does not state a usage condition.

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