milehost_list_files

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

With no annotations, the description carries the transparency burden. It correctly implies a read-only operation by saying it lists files and directories, but it does not disclose connection/authentication assumptions, output structure, or any special behavior beyond the listing itself. No contradiction with annotations exists because none were provided.

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 only two sentences, with the core behavior front-loaded and the intended agent use stated immediately after. There is no redundant filler or unnecessary repetition.

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 simple listing tool with zero required parameters and full schema coverage, this is minimally adequate. However, it relies on the schema for path and folder semantics, does not mention what the response looks like, and does not address when to prefer related sibling tools.

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 already describes all four parameters completely, so the baseline is 3. The tool description adds no additional parameter-level meaning beyond clarifying that listing happens inside the user's remote container.

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 verb ('Lists') and resource ('files and directories inside the user remote container on MileHost'), making the tool's purpose clear. It is distinguishable from server-level siblings like milehost_list_servers, but it does not explicitly contrast with milehost_list_folders, which could overlap with 'directories'.

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' sentence explicitly tells agents to use this tool for exploring remote directory structure and verifying deployed files on MileHost. This provides clear context for when to use it, but it does not mention exclusions or alternatives such as milehost_list_folders.

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