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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds the returned field set and the enrollment linkage, but nothing beyond annotations and the output schema (e.g., pagination or ordering) is disclosed.

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?

Two short clauses: the resource/fields come first, then the actionable follow-up hint. Zero waste and 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 zero params, an output schema carrying the return structure, and annotations covering safety, the description is nearly complete for this simple list tool. The only minor gap is thin guidance on when to choose this versus other list_* tools.

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?

There are zero parameters, so the baseline is 4. The description correctly implies no filtering inputs are needed, matching the empty schema, and adds no misleading parameter claims.

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 names the resource (automations in the workspace) and enumerates the returned fields (id, name, status), making the tool's scope concrete. It also connects to the sibling enroll_automation, helping distinguish it, though the verb 'list' is only implied rather than stated in the description text.

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 hints at downstream usage ('use an automation id or name with enroll_automation'), which implies this tool is a lookup for enrollment. However, it never states when to prefer this over the other list_* siblings or any explicit conditions/exclusions, leaving usage only implicitly guided.

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