update_suppression_rule

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

No annotations provided; description highlights write operation and safety check, but lacks details on error behavior, idempotency, or permission requirements for a mutation tool.

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?

Single, clear sentence that immediately conveys purpose and critical requirement (confirm). Front-loaded and efficient.

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?

Lacks details on conditions object format, error handling, return value, and prerequisites. Given no output schema and complexity, the description is incomplete for reliable invocation.

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 50%; description adds minimal value beyond schema. It lists fields but does not explain conditions structure or provide extra semantics for undocumented parameters.

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 verb 'update' and resource 'suppression rule', and lists updatable fields (name, description, conditions). Distinguishes from siblings like create and delete.

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?

Specifies that it requires 'confirm: true' and is a WRITE OPERATION, implying user approval needed. No explicit when-not-to-use or alternative tools mentioned, but context is adequate.

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