update_monitor

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

No annotations exist, so description carries burden. It notes immutable fields but lacks details on side effects, idempotency, or whether previous assignments are cleared if not specified. Moderate transparency.

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?

Three sentences, no fluff, purpose-first. Efficiently communicates key constraints and parameter usage.

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 it's an update tool with output schema, description covers main aspects: modifiable fields, restrictions, webhook source. Could mention partial update behavior, but still fairly complete.

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%, but description adds context: webhook IDs are from create_webhook/list_webhooks and that limit has a minimum of 10 (echoed from schema but reinforced). Adds value beyond raw schema.

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 explicitly states 'Update a monitor's webhook assignments and per-run limit,' clearly indicating the verb and specific resources. It distinguishes from sibling tools like create_monitor, delete_monitor, etc.

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?

Provides explicit guidance on what cannot be modified (schedule and reference_job_id) and advises that webhooks are centralized with IDs from create_webhook/list_webhooks. This helps the agent decide when to use this tool.

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