list_files

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

No annotations provided, so description carries full burden. It discloses that returns are lightweight records (path, type, level, sign) without loading full bodies. Missing details like pagination or performance but sufficient for the tool's scope.

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?

Three sentences, each serving a purpose: state action/return, describe returns, and provide usage/alternatives. No redundancy, front-loaded key info.

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?

Covers purpose, return values, main use cases, and sibling differentiation. Lacks output schema and pagination details, but with 4 optional parameters and clear description, it's reasonably 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 coverage is 100%, so baseline is 3. Description adds context for no_metadata but doesn't deeply elaborate on other parameters. No extra meaning beyond schema for level, sign, subfolder.

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 lists notes already known to the local index. It distinguishes from sibling tools by explicitly suggesting get_children or get_parents for graph traversal.

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?

Explicitly tells when to use the tool (for inventory, filtering, finding files to inspect next) and provides a specific use case (set no_metadata=true to find Markdown files without YAML metadata). Also advises against using this tool for graph traversal, directing to siblings.

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