delimit_notify_routing

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

No annotations provided, but the description explicitly discloses side effects per action: 'action=\"configure\" writes via ai.notify.save_routing_config', 'action=\"test\" sends test notifications', and 'action=\"status\" is read-only'. This covers write operations and read-only behavior. Could mention auth or error handling but is sufficient.

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?

Highly structured into sections: purpose, when to use, when not to use, sibling contrast, side effects. Every sentence adds value with no repetition or fluff.

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 an output schema exists, return values are covered. The description provides all necessary context: purpose, usage guidelines, sibling differentiation, side effects, and parameter context. Nothing essential is missing for an AI agent to correctly select and invoke this tool.

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 has 100% coverage with descriptions for all 5 parameters. The description adds context by explaining the config parameter's use with configure action and webhook_url, email_to, from_account for test action, tying parameters to their respective actions.

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 'Manage impact-based notification routing' and specifies inspecting or updating rules that route change alerts by severity. It distinguishes from sibling tools delimit_notify and delimit_notify_inbox, making the purpose unambiguous.

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 provides both 'When to use' and 'When NOT to use' sections with specific sibling tool names. Gives sibling contrast explaining the roles of delimit_notify, delimit_notify_inbox, and this tool.

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