gaea_list_outputs

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly signals a non-destructive list operation scoped to a build directory, which is useful. However, it does not disclose whether listing is recursive, whether hidden files or subdirectories are included, how missing directories are handled, or what the return values look like.

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 clear sentence with no filler. It is front-loaded and every word contributes to stating the operation.

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 tool with no annotations, no output schema, and one undocumented parameter, the description is too sparse to support reliable invocation. It omits return format, preconditions such as a completed build, and meaningful parameter semantics beyond naming the directory.

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 0%, and the description only restates that outputDir refers to a Gaea build directory, adding little beyond the parameter name. It does not clarify the expected path format, whether the path may be absolute or relative, or what happens when the directory does not exist.

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?

States a specific verb and resource: it lists output files in a Gaea build directory. The operation is clearly a read-only enumeration, and the verb 'List' helps separate it from mutating siblings like gaea_set_build_output. However, it does not explicitly contrast with related sibling tools such as gaea_list_graphs or gaea_set_build_output.

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 guidance is provided about when to call this tool or when to prefer an alternative like gaea_list_graphs or gaea_set_build_output. The description implies it should be used to inspect generated outputs, but it never says this or mentions any prerequisites.

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