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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds value beyond that by disclosing a cross-tool behavioral detail: a switched-off automation carries the activation_token that activate_automation requires, which is exactly the kind of linkage annotations cannot express. It does not discuss pagination or the meaning of 'total', but that is a minor omission given the annotation coverage.

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 purpose is front-loaded in a single strong sentence, and the Args section is tight. However, the trailing Returns block restates the output structure even though a full output schema is already supplied, so a meaningful chunk of the text is redundant rather than additive.

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 two-parameter read-only listing tool with a full output schema, the definition supplies everything needed: purpose, both parameter meanings, and the activation_token handoff to activate_automation. The only slack is the duplicated return-value enumeration, which the output schema already covers.

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 0%, so the description must carry the full burden, and it does: workspace_id is explained as limiting to one workspace the user owns, and automation_id as returning one automation plus its recent output. Both parameters gain semantics absent from the bare anyOf string definitions. The explanations are functional rather than exhaustive (no format or ID examples), which keeps it just below a 5.

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 opens with a specific verb and resource ('List the user's Clarifo Automate automations') and then enumerates exactly what each entry contains: what it does, enabled state, schedule, next run, latest run, and produced documents for a single automation_id. That level of detail lets an agent distinguish this listing tool from siblings like activate_automation or create_automation_draft without opening the 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?

It gives clear conditional usage for both parameters: workspace_id narrows to one owned workspace, automation_id switches to a single-automation view with recent output. It also names the downstream tool (activate_automation) and the activation_token that connects the two, which is real handoff guidance. It stops short of stating explicit exclusions or when-not-to-use conditions.

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