List folders

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

With no annotations, the description carries the burden of behavioral disclosure. 'List all folders' clearly indicates a read-only enumeration, but it does not mention ordering, pagination, or whether the response contains folder metadata, counts, or other details. For a simple list operation this is adequate but not richly transparent.

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 concise sentence that immediately states both the action and the scope. Every word contributes meaning, and there is no redundancy with the title or sibling context.

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 parameterless list tool with no output schema, the description is largely sufficient: it names the resource and the organizing concept. It would be more complete with an explicit statement about the return type or the distinction from get_folder, but the low complexity keeps these gaps minor.

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 zero parameters, so the baseline score is 4. The description adds no parameter-level details, but none are needed because the tool takes no inputs.

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 a specific verb ('List') and resource ('all folders used to organize cron jobs'), which makes the tool's basic purpose unambiguous. However, it does not explicitly distinguish itself from the sibling get_folder, which also deals with folders, so it misses the top score.

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 phrase 'all folders' implies the tool is for retrieving a complete folder listing rather than a single folder, and naming the cron-job organization purpose gives helpful context. There is no explicit guidance about when to choose this tool over get_folder or how it relates to the other sibling tools, leaving usage mostly implied.

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