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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the permission gate (editors/owners) and the shape of each record (trigger type, on/off state, last run), which tells the agent what it will actually see.

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 sentences, no filler. The returned-field summary is front-loaded and the access restriction follows it, so the agent gets the substance before the caveat.

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 single-parameter read tool with full annotation coverage and no output schema, the description supplies the essentials: what is listed, what each entry contains, and who may call it. Only the pagination/result-size question goes unanswered, which is a minor gap at this complexity level.

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 single baseId parameter is undocumented in the schema. The phrase "of a base" does imply that baseId identifies the target base, but the description adds nothing about format, accepted ID types, or behavior for an invalid base — the minimum compensation needed at this coverage level.

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 of a base) and enumerates what each entry includes: trigger type, enabled status, and last run. It implicitly distinguishes itself from the singular get_automation by being a bulk listing, but never says so explicitly, so sibling differentiation is left to inference.

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?

"Editors and owners only" gives an access prerequisite, which is useful context for when the call will succeed. However, there is no explicit guidance on when to use this versus get_automation or update_automation, and no mention of pagination or volume expectations for a list operation.

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