List files on a device

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the useful constraint that paths are confined to the authenticated user's remote $HOME, but says nothing about recursion depth, sorting, result limits, or error behavior on an unreachable device.

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?

A single front-loaded sentence with zero redundant wording; the remote scope is established immediately.

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 three-parameter read tool with full schema coverage and annotations carrying the safety profile, this is adequate but thin. An agent still cannot tell whether the listing is recursive, paginated, or what happens when the device_id is unauthorized or offline.

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%, so all three parameters are already well documented in the schema, including the $HOME-relative semantics of path. The description's phrasing duplicates rather than extends the schema and adds no new detail about path formatting or show_hidden interaction.

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 and resource ("List files and directories") plus a scope qualifier ("relative to $HOME"), which is enough to distinguish it from write-side siblings like pi_file_write or pi_directory_create. It does not explicitly contrast with the closest read-side sibling, pi_file_read, nor mention which device-context tools must be used first.

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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as pi_file_read for inspecting a single file. The only implicit routing signal is the $HOME-relative scoping, which an agent must infer.

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