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

Goes well beyond the annotations by disclosing the two-phase preview/write contract, that a tokenless call mutates nothing and returns the full resulting config plus changed fields, that untouched values are preserved, and that timezone is preserved rather than updatable. This is exactly the mutation-safety context annotations alone cannot convey, and it is consistent with idempotentHint=true.

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?

Four dense sentences, front-loaded with the two-phase constraint, and every sentence adds an operative rule (no inference, timezone handling, minimum change, preview/token flow). No filler.

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 15-param mutation with no output schema, the description nails the safety-critical flow and the preservation semantics. It stops short of characterizing the domain fields the agent must actually set, so it is strong but not fully 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?

With only 40% schema coverage across 15 params, the description carries real weight: it explains automation_id, confirmation_token, the 'at least one changed value' rule, and the non-parameter status of timezone. However, the majority of parameters (topic, weekday, platform, frequency, daily_time, day_of_month, recipient_email, use_account_email, uid) get no semantic help in the description, leaving a substantial gap.

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 states a specific verb+resource ('explicit two-phase write' of a trend research automation's configuration) and makes the preview-then-write nature unambiguous. It never explicitly says what resource is being updated (only 'configurable values' and 'resulting configuration'), and it does not distinguish itself from the sibling update_automation, so a 4 is right.

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?

Clear when-to-use rules: supply automation_id plus at least one explicit changed value, never infer or default values, and only pass confirmation_token after later user confirmation. It gives no guidance on when to choose this over the closely named update_automation sibling, which keeps it from a 5.

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