List Target Tree

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds that the read is 'confined' and returns relative-path to sha256 pairs, which are behavioral details not in the annotations. It does not disclose traversal edge cases (e.g., symlinks or hidden files), but the annotation safety profile lowers the burden.

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?

Two short sentences carry all the content, with the core action front-loaded and the usage context in the second sentence. There is no filler or repetition of the schema field names.

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?

With an output schema present and read-only annotations, the description covers purpose and usage adequately. However, the complete absence of parameter semantics for both required arguments leaves an agent guessing about valid values for target_relative_dir, so the description is only minimally complete.

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 0%, and the description never explains target_root_id or target_relative_dir beyond what their names already imply. There is no format guidance, relationship between the two parameters, or example, so the description fails to compensate for the schema gap.

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 opens with a specific verb and resource: 'Read a confined target directory tree as relative-path to sha256.' It states both the scope and the output shape, and the reference to prepare_strategy_changes separates it from other read/list tools among the siblings.

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?

It explicitly says to use the tool before prepare_strategy_changes to construct expected_target_hashes preimages, giving a clear trigger condition. It does not spell out when not to use it or name alternatives, so it stops one step short of a full 5.

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