List Script Processes

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, which fully cover the safety profile. The description adds minimal behavioral context (e.g., 'recent' is vague, no mention of pagination or limits), so it provides some value but not significant beyond annotations.

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 a single sentence that directly states the purpose with no extraneous text. It is appropriately concise for a simple list tool, though it could be slightly improved by adding brief usage context without becoming verbose.

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 tool's low complexity, presence of an output schema (not shown), and comprehensive annotations, the description is minimally adequate. However, it lacks explanation of what constitutes a 'process' or the time range for 'recent,' leaving minor gaps in context.

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%, with all parameters already described in the input schema (user_google_email, page_size, script_id). The description adds no additional parameter meaning, so it meets the baseline of 3 without exceeding.

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 the tool lists recent execution processes for user's scripts. The verb 'lists' and resource 'execution processes' are specific, and it distinguishes itself from sibling tools like list_script_projects or list_versions by focusing on script executions.

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 does not provide guidance on when to use this tool versus alternatives, nor does it mention prerequisites or context like monitoring script runs. The purpose is clear, but the lack of usage direction keeps it from scoring higher.

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