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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered. "Does not start or retry work" is largely a restatement of that read-only contract, and the referenced return fields (status, reserved credits, failures) are already covered by the output schema, so genuinely new behavioral context is thin.

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 read scope is front-loaded and the non-goal follows immediately. Every clause earns its place.

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 an output schema present and rich annotations, the description need only frame purpose and scope, which it does. The only real gap is filter/pagination semantics for the four undocumented parameters, which is a minor omission for an otherwise complete listing tool.

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% across 4 parameters, so the description must carry the burden, and it does not: limit, cursor, brandId and automationId are never mentioned or explained. Nothing in the description clarifies that automationId filters to a single automation or that cursor/limit drive pagination.

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+resource ("Read recent automation runs") and enumerates what the read surfaces (status, reserved credits, failures), which clearly separates it from get_automation_run (singular, detail) and control_automation. It stops short of naming those siblings explicitly, so it is clear but not fully self-differentiating.

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?

"Does not start or retry work" draws an explicit negative boundary that tells the agent when this tool is not the right pick. However, it does not name the alternative (e.g. control_automation) to route to, so the when-to-use side is only implicit.

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