update_notification

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

Describes key behavior: passing None leaves fields unchanged, only explicit values sent in PUT body. Warns about plan-specific alert_type. No annotations provided, so description carries burden and does it well, though could mention authorization needs.

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?

Structured with general description and Args section. Front-loads critical 'pass None' behavior. A bit lengthy but each sentence adds value; could be slightly more concise.

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?

Covers parameters, return value (JSON string), and usage guidance. No mention of error handling or validation beyond alert_type warning. Output schema exists, so return details are sufficient. Comprehensive for a mutation tool with 10 parameters.

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?

With 0% schema description coverage, the description provides thorough parameter documentation, including default behaviors (email defaults to user's primary), common values for alert_type (with plan-specific warning), and clarifies that unknown alert_type values warn but do not reject.

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 'Update a notification rule' and describes the purpose of notification rules. Distinguishes from sibling tools like create_notification and delete_notification by specifying its use case.

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 explains when to use this tool: 'rewire targets, change triggering events, or silence a noisy rule without deleting it'. Also contrasts with creating/deleting.

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