Enable or disable Scaleway Audit Trail alert rules

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

Annotations already set readOnlyHint: false, destructiveHint: false, idempotentHint: true. The description adds critical behavioral context: idempotent partial update behavior, all-or-nothing failure (HTTP 404 on unknown ID), and explicit permissions requirements beyond AuditTrailReadOnly. The 'Live-verified' timestamp adds credibility. No contradiction with annotations.

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?

Description is front-loaded with the core purpose, then provides behavioral contrast, troubleshooting, and permissions context. Every sentence adds value. Slightly dense with technical details but remains efficient for an AI agent.

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?

For a 3-parameter tool with no output schema, the description covers all key dimensions: purpose, differentiation from sibling, parameter semantics, error behavior, permissions requirements, and data source. The agent has enough context to invoke correctly without ambiguity.

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 description coverage is 100%, so baseline is 3. The description adds value by explaining the enabled parameter semantics ('true: enable exactly these rules... false: disable exactly these rules') and the rule_ids source (from list_alert_rules), going beyond the schema's basic description. The region default value is also clarified. No output schema needed.

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?

Description states the tool enables/disables specific preconfigured alert rules by ID, clearly distinguishing from the sibling scaleway_audit_replace_enabled_alert_rules. The verb 'Enable or disable' combined with 'Touches ONLY the listed rules' makes the specific resource and scope 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 tells when to use this tool vs scaleway_audit_replace_enabled_alert_rules, provides where to get rule IDs (scaleway_audit_list_alert_rules), and gives detailed troubleshooting for permissions errors with a specific sibling tool reference (scaleway_iam_set_policy_rules).

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