addToAllowlist

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

Discloses bypassing effect but lacks details on side effects, idempotency, or limits. No annotations so description carries burden, but it is adequate for a simple add operation.

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 concise sentences: first states purpose, second provides safety note. No redundant words.

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?

Adequate for a simple add tool with 2 parameters and no output schema. Missing info on behavior if domain already in allowlist, but overall sufficient.

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 100% with clear descriptions for both parameters. Description adds no extra meaning beyond what schema provides (e.g., clarifies 'domain' for id, but schema already says 'domain name or identifier').

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?

Clear verb 'adds', specific resource 'domain to profile's allowlist', and effect 'bypasses all blocking'. Differentiates from siblings like addToDenylist.

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?

Explicitly states 'Only use with designated test profiles', providing a strong when-not condition. Does not explicitly name alternatives but context implies other add tools.

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