dnc_update_settings

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

With no annotations, the description carries the full behavioral burden. It explains key behavior: protection_enabled=false logs but does not enforce DNC checks, and auto_add_inbound_optouts enables inbound STOP detection. It does not mention null-handling or other side effects, but provides valuable context beyond the schema.

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 two short sentences plus a concise args list. Every word adds value, with no fluff or repetition. The structure is clear and front-loaded with the purpose.

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 2-parameter tool, the description covers both parameters' functionality and effects. It doesn't explain the null-null case or explicitly mention return/response, but an output schema exists. Minor gaps in usage guidance prevent a 5.

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 description coverage is 0%, but the description fully explains both parameters: protection_enabled as a master switch with explicit consequences when false, and auto_add_inbound_optouts as a watcher for STOP-style language. This adds rich meaning well beyond the schema's type/default info.

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 'Toggles DNC protection and inbound STOP auto-detection,' specifying the verb and resource. It distinguishes itself from sibling tools like dnc_get_settings (read) and dnc_add_entry (add) by focusing on updating settings.

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 usage for changing DNC settings but does not explicitly state when to use this tool versus alternatives like dnc_get_settings for reading or dnc_check for lookups. No alternatives are mentioned, so guidance is only implicit.

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