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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds context beyond them: replacement semantics when automation_id is supplied, pausing via active=false, the platform scope (Instagram and Facebook), and a human-in-the-loop requirement to show the message before saving. It does not spell out what is overwritten/lost when replacing an existing rule.

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 short sentences, each earning its place: purpose first, then the replace/pause conditions, then the human-confirmation requirement. No filler and the key constraints are front-loaded.

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?

With no output schema and a destructive mutation over a nested rule object, the description covers purpose, replacement, pausing and the confirm-with-user step, which is decent. It remains thin on the nested rule configuration options and on what a replacement destroys, which matters for an operation the annotations mark destructive.

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 40%, below the 50% threshold, so the description must compensate. It explains two of the optional parameters well (automation_id and active) but says nothing about brand_id, operation_id retry semantics, or the many fields inside the nested rule object (keywords, match_mode, trigger, follower_status, button fields).

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?

States a specific verb+resource: creates a rule that sends a private DM when someone comments a keyword, scoped to Instagram and Facebook. The automation_id replacement case is named. It stops short of naming the sibling it is not (e.g. start_automation_setup or create_comment_bot), so differentiation is implicit rather than explicit.

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?

Gives two conditional usage rules ('con automation_id la reemplaza' and 'active=false la pausa'), which is real when-to-use guidance. There is no guidance on when to use this versus list_dm_automations, start_automation_setup or create_comment_bot, and no prerequisites (e.g. needing a connection/account first).

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