milehost_list_folders

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

No annotations are provided, so the description carries the burden. The word 'Lists' and 'inspect' imply a read-only, non-mutating operation, which is useful. However, it does not disclose authentication requirements, error behavior, or whether the call has side effects beyond listing.

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 short and front-loaded with the main purpose, followed by a directive sentence. The 'AI AGENT MANDATE' phrasing is somewhat redundant, but it does reinforce the intended usage without adding bulk.

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 low-complexity list tool with two optional parameters and no output schema, the description gives the core idea and even names folder_id. Still, without an output schema, it would benefit from describing the response shape or noting how it differs from milehost_list_servers.

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 api_key and api_url already clearly documented. The description adds no additional parameter-level meaning, so the baseline of 3 is appropriate.

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 a specific action ('Lists all available user containers, servers, and folders on MileHost') and names the resource. However, the overlap with the sibling milehost_list_servers is not resolved; an agent may not know which tool to choose if it only needs servers.

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 'AI AGENT MANDATE' provides a clear use case: call it to inspect available containers and their folder_id. But it does not mention when not to use it, nor does it contrast this tool with milehost_list_servers or other siblings, so alternative selection guidance is missing.

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