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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is covered; the description still contributes by disclosing the full shape of what is returned (enabled / dry-run / seven named action groups / last-activity timestamp), which an agent cannot infer from the annotations. It does not describe pagination or error behavior, but none is plausibly needed for a single-profile status read.

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?

One front-loaded sentence that names the resource first, then the payload, then the parameter prerequisite. Every clause carries information an agent needs; nothing is restated from the title or annotations.

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?

There is no output schema, so the description carries the burden of describing return values and does so field by field, including the seven named action groups. Combined with the annotations covering the read-only profile, an agent has everything needed to call this correctly.

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% and both parameters are already documented there, including the "from list_profiles" sourcing note the description repeats. The description adds no semantics beyond the schema (e.g., when to supply profile_pk to disambiguate duplicates), so the baseline of 3 applies.

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 and resource ("Get the automatic-mode configuration for an Amazon Ads profile") and then enumerates exactly what that configuration contains: enabled flag, dry-run mode, per-action-group toggles, and last-activity timestamp. That enumeration distinguishes it from get_automation_activity (a log) and prepare_automation_settings_v1 (the write counterpart) without needing to open either schema.

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?

The description implies when it applies (reading automation state per profile) but never states when to use it versus siblings such as get_automation_activity or get_optimization_settings. The one explicit usage instruction is a provenance rule — "profile_id must come from list_profiles" — which is a prerequisite, not a when-to-use rule.

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