yaaif_skill_file_tree

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'List' clearly signals a read-only operation, but the description does not mention return format, recursion depth, or whether hidden/system files are included. It covers the basic behavior but omits potentially useful detail.

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?

One concise sentence with no redundant words. The resource, verb, and workspace scope are all present and front-loaded. Nothing extraneous is included.

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?

The core listing action is stated, but the tool is incomplete for an agent because the only parameter is completely undocumented and no output shape or traversal semantics are described. For a tool with a single optional parameter, this ambiguity is significant.

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 single 'path' parameter has zero schema description coverage, and the description never mentions it. An agent cannot determine what the path should be relative to, its expected format, or what the default behavior is when omitted. The description adds no semantic value for the only parameter.

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 uses a specific verb and resource ('List the tenant skill files tree') and adds a scoping parenthetical ('Advanced Skills workspace'). It is clear what the tool does, though it does not explicitly distinguish itself from tools like yaaif_skill_list or yaaif_files_list.

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?

No explicit when-to-use guidance or named alternatives, but the parenthetical 'Advanced Skills workspace' implies it is intended for browsing the skill workspace file tree. The usage context is faintly implied rather than stated, so agents are left to infer relation to sibling file and skill tools.

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