automations_list_automation_traces

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

Adds behavioral detail: accepts bare id or 'automation.<id>' format. Clarifies output is summaries/recent runs. No annotations provided, but this compensates somewhat.

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 sentences, front-loaded purpose then format detail. No wasted 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 output schema exists, description covers purpose and id format sufficiently. Could mention relationship to get_automation_trace for completeness, but adequate for a simple list 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?

Adds critical meaning beyond schema: specifies accepted formats for automation_id (bare id or prefixed). Schema only says string, so this fully compensates for 0% schema coverage.

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?

Description clearly states verb 'List', resource 'trace summaries (recent runs)', and scope 'for an automation'. Differentiates from siblings like automations_get_automation_trace by indicating it returns summaries.

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?

No explicit when-to-use or when-not-to-use guidance. Implies usage for listing recent runs, but doesn't mention alternatives like automations_get_automation_trace for detailed traces.

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