set_model_denylist

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

No annotations are provided, so the description bears full responsibility. It reveals the tool is a WRITE operation with medium risk, and that the denylist replaces the entire list with patterns that always win. However, it does not disclose persistence or effect on currently running models.

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?

The description is extremely concise: a single line with the WRITE tag and purpose, followed by a parameter description. Every word adds value, with no redundancy. It is front-loaded with the most important 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?

Given the low complexity (one parameter, no output schema), the description covers the tool's core purpose and behavior adequately. It explains the replacement action and pattern syntax, though it could hint at return values or confirm whether the change is applied globally or session-based.

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 input schema has 0% description coverage, so the description entirely compensates by explaining that 'models' are 'Shell-glob patterns of forbidden model names', providing essential semantics beyond the schema's minimal definition.

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?

The description clearly states the tool replaces the model denylist, using specific verb ('Replace') and resource ('model denylist'), and distinguishes it from sibling tools like set_model_allowlist by noting 'deny patterns always win'.

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 description implies that the denylist overrides the allowlist ('always win'), but does not explicitly state when to use this tool over others (e.g., set_model_allowlist) or mention prerequisites or consequences of replacement.

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