addToDenylist

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

No annotations provided. Description indicates the tool mutates state (adds/blocking) but does not disclose idempotency, reversibility, or behavior on duplicate entries. Safety note hints at impact but lacks detail.

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 front-load the purpose and a critical safety caveat. No redundant or extraneous content.

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 simple mutating tool with no output schema, the description is complete enough. The safety note provides necessary context, and no additional information is needed.

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 covers both parameters with descriptions (profile_id, id). The tool description does not add additional meaning beyond schema, meeting baseline for high coverage.

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?

Description clearly states 'Adds a domain to the profile's denylist (blocks the domain)', specifying the verb, resource, and effect. It distinguishes from siblings like addToAllowlist and removeFromDenylist.

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?

Safety note 'Only use with designated test profiles' provides explicit context for appropriate use. While it doesn't list alternatives, the note implies constraints that guide selection.

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