Get automation endpoint-results overview

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

The description does not add behavioral traits beyond what annotations already provide. Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description's mention of 'rollup' implies aggregation but doesn't contradict or disclose additional behavioral nuances like pagination or 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 extremely concise with only two sentences. The first sentence states the core purpose, and the second provides an alternative tool reference. No unnecessary words.

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?

Given the output schema exists, annotations cover safety, and schema covers parameters, the description is fully complete. It tells the agent exactly what the tool does and how it relates to a sibling tool, with no missing information for agent comprehension.

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% so the schema already documents parameters. The description does not add extra meaning or context for parameters beyond what the schema provides, so baseline 3 is appropriate.

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 clearly states 'Per-endpoint result rollup for an instance', specifying the exact scope and resource. It also distinguishes from the sibling tool action1_get_automation_output by mentioning that tool is for stdout, providing clear differentiation.

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?

The description explicitly tells when to use this tool (for per-endpoint rollup) and when to use an alternative ('Use action1_get_automation_output for stdout'), providing clear guidance on tool selection.

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