addToDenylist

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

No annotations provided, so description bears full burden. Describes the basic mutation but does not disclose whether the operation is idempotent, overwrites existing entries, or requires specific permissions. Adequate but not detailed.

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 no redundancy. Front-loaded with action and safety notice. Every word 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?

Given the tool is a simple add operation with no output schema, the description is sufficient. Does not explain behavior on duplicate entries or error conditions, but these are implied for a denylist. Works well given the sibling count.

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?

Input schema already provides descriptions for both parameters (100% coverage). The tool description adds little beyond the schema: it mentions 'domain' but the schema says 'domain name or identifier'. Baseline 3 is appropriate.

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?

Clearly states the action (adds a domain), the resource (profile's denylist), and the effect (blocks the domain). Distinguishes from sibling tools like addToAllowlist.

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?

Includes a safety note restricting use to designated test profiles, which provides explicit usage context. Lacks explicit alternatives but is sufficient for a simple mutation.

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