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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so 'Changes nothing' is largely redundant. The description does add behavior not in annotations: the ordering guarantee (most recently used first) and the concrete paging model (10 per page, up to 25, continue with next_cursor), which are real operational facts.

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 tight sentences with zero filler; the core purpose is front-loaded, and paging plus the read-only note are packed into the same compact statement.

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 no output schema, the description carries the burden of describing returns; it covers count, ordering and row granularity but not which fields each automation row contains. For a low-risk read-only lister with full schema coverage on inputs, this is nearly complete.

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 100% and the description merely restates what the schema documents (limit up to 25, cursor as next_cursor from the previous page). It adds no format or edge-case meaning beyond the schema, 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 (lists the user's Automations) plus scope, result shape ('one row each'), and ordering ('most recently used first'). No sibling tool lists automations, so there is no ambiguity to disambiguate, and the agent can tell exactly what comes back.

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?

Usage is only implied: the board_id requirement (from Open Shoot Board or context) and the paging hints suggest enumerating automations on a board and browsing when there are more than 10. There is no explicit statement of when to prefer this over other listing tools or any exclusion, so an agent must infer the trigger.

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