List SSH Directory

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the description only needs to add extra context. It does so by noting the operation is 'bounded' and that results are structured only when the remote find utility is available, which are useful behavioral details beyond the annotations. The description does not contradict any annotation.

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 two sentences long, front-loaded with the main action, and contains no wasted words. It efficiently communicates the core purpose and a key behavioral condition without redundancy.

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?

While the output schema covers return structure, the description lacks clarity on parameter usage, the meaning of 'bounded,' and what happens when the find utility is unavailable. These gaps are significant given 0% schema description coverage and the tool's reliance on a remote utility. The description could be more complete with explicit parameter notes and fallback behavior.

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 schema description coverage is 0%, so the description must compensate by explaining key parameters like path and limit. It does not mention any parameter meanings or usage requirements. The only hint is 'bounded' possibly hinting at limit, but it is not explicit. This is insufficient for a 5-parameter tool with zero schema explanations.

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 the tool's purpose: 'Lists a bounded remote directory through SSH and returns structured entry summaries when the remote find utility is available.' It uses a specific verb (lists), identifies the resource (remote directory), and adds a conditional detail about the find utility, distinguishing it from general exec or file operations.

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 description implies this tool is for listing directories, but it does not explicitly state when to use it over alternatives like exec or read_file. It does mention 'Safe in dev/test/prod,' which hints at safe execution contexts, but lacks explicit when-not and alternative guidance. This is adequate but not thorough.

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