recent_executions

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

With no annotations provided, the description adds behavioral context by stating it uses execution metadata, requires no extra scope, and excludes console.log output. However, it does not disclose default ordering, pagination behavior, or potential errors, leaving some burden unmet.

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 three short sentences, front-loaded with the core purpose and followed by a useful filter and a key limitation. No filler or repetition.

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?

For a list tool without an output schema, the description specifies the returned fields, the failure filter, and a notable limitation, covering the essential context. It does not discuss pagination semantics, but the pageToken parameter partially covers that; overall adequate.

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?

Input schema already describes all five parameters, and the description adds only the filter-for-failures option (matching onlyFailures) without syntax details. It does not compensate further, so baseline 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?

Description states 'List recent executions of an Apps Script project' with a specific verb and resource, and enumerates returned fields (function, status, start time, duration). This distinguishes it from execution-related siblings like script_run (which runs) and process-listing tools.

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 notes that it can optionally filter to failures and explicitly states it does not include console.log output, which helps agents decide when to use this tool. It does not explicitly name alternatives or exclusion conditions beyond the log limitation, but the context is clear.

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