list_cycle_folders

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

Discloses that project/version accept names or ids, prefers ids, and that -1 means Unscheduled. Specifies return fields: ID, folderName, folderDescription, and execution summaries. Lacks explanation of pagination (limit/offset) behavior, but overall provides good context for a list operation without 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?

Two concise sentences: first states core purpose, second provides parameter and return details. No redundancy, every sentence adds value.

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?

Covers main behavior and return structure, but omits pagination behavior, error scenarios, and ordering. Given no output schema, description explains return fields, but gaps remain for a 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 meaning for project and version parameters (accepts names/ids, special value). Does not explain cycle_id, limit, or offset beyond schema types. With 0% schema description coverage, this partial compensation is adequate but not complete.

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 'List the folders within a cycle' with a specific verb and resource. It distinguishes from siblings like list_cycles and list_executions. Additional details about parameter handling and return structure reinforce purpose.

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 guidance on when to use this tool versus alternatives. The description hints at input handling (prefer ids, -1 for Unscheduled) but does not clarify when to choose this over other list tools or mention any prerequisites or constraints.

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