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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful behavioral context: each row represents one firing, the possible execution statuses are listed, and API-key scope `automations:read` is disclosed. Minor gaps remain around pagination or log-size limits.

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 action and row structure, then adds usage rationale and scope. It is efficient overall, though the UI summary-stats note is slightly tangential and costs a small amount of space.

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?

There is no output schema, so the description carries the return-value burden and does a good job listing row fields and execution statuses. It is nearly complete, but does not mention result volume, pagination, or retention behavior for the audit log.

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 100%, so the schema already documents account, workspace, and identifier semantics thoroughly. The description only implies the automation identifier via 'for an automation' and adds no additional parameter-level detail beyond the schema.

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 states a specific verb and resource: fetch the execution audit log for an automation. It also describes the row contents (timestamp, triggering task, trigger type, status, per-action detail), which clearly distinguishes this from the sibling pm_get_automation configuration tool.

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 gives a clear usage scenario: debug 'did my automation run?' and calls itself the authoritative answer because the UI does not show summary stats. It does not explicitly name alternatives such as pm_get_automation or state when not to use this tool, so it falls short of a 5.

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