update_notification_policy

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

With no annotations, the description must disclose behaviors like idempotency, mutation effects, auth requirements, or error states. It only says 'update', leaving the agent unaware of partial update semantics or side effects.

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 a single sentence, which is concise, but given the complexity of the tool (nested body with multiple optional fields), it omits critical information. It is not well-structured for an agent to quickly understand key details.

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?

Despite having an output schema, the description fails to convey essential context: what happens if fields are omitted (merge vs replace), validation rules, or behavior when policy_id is invalid. The tool is non-trivial and the description is inadequate.

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?

The input schema includes descriptions for many sub-properties (e.g., 'matchRules', 'escalation'), so schema coverage is high. The tool description adds no additional meaning beyond the schema, but the schema itself provides adequate parameter semantics.

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 'Update a notification policy' clearly states the action (update) and the resource (notification policy). It distinguishes from create/delete/get by the verb, but does not clarify specifics like partial vs full update.

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?

No guidance on when to use this tool vs. alternatives like create_notification_policy or test_notification_policy. No prerequisites or postconditions mentioned.

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