list_nested_executions

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

The description discloses the return format and the recurse behavior, providing useful context beyond the schema. However, with no annotations, it does not explicitly confirm read-only behavior or potential side effects, leaving some uncertainty.

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 well-structured with Args, Returns, and Example sections. Each sentence adds value, and the examples clarify usage without unnecessary verbosity.

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 simplicity of a list operation, the description covers purpose, parameters, return format, and examples. The output schema is implied by the return description, and no significant gaps remain.

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?

The input schema has no descriptions, but the description explains both execution_rid and recurse in detail, including default behavior and an example, fully compensating for the 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?

The description states 'List all child (nested) executions of an execution', clearly specifying the verb, resource, and scope. It distinguishes from sibling tools like list_asset_executions by focusing on nested executions of a parent execution.

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 implies the use case through its examples but does not explicitly state when to use this tool versus alternatives or when not to use it. No exclusions are mentioned.

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