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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context by stating that the call is read-only, describing the returned automation fields, explaining pagination, and noting that MCP calls consume no Adrails credits.

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 description is front-loaded with the core list operation, then quickly covers pagination, alternatives, and cost. Every sentence adds actionable information, and there is no repetition or 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 read-only list tool with no output schema, the description is complete enough: it names the returned fields, explains pagination, identifies alternatives for mutation and preview, and notes credit usage. The remaining parameter details are adequately covered by the input schema.

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 coverage is 75%, so the schema already documents most parameters, including after as the previous page's nextCursor. The description reinforces pagination but does not add meaning for accountIds, userStatement, or idempotencyKey, and idempotency is irrelevant for this read-only call.

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 gives a specific verb and resource: it lists workspace automations with named return fields and templates, capped at 100. It also distinguishes this read operation from workflows_manage and workflows_preview, so an agent can select it without opening sibling schemas.

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 explicitly routes write operations to workflows_manage and inspection of a proposed run to workflows_preview. Pagination guidance is also included via nextCursor and after, leaving little ambiguity about when and how to use this tool.

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