list_files

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

No annotations are provided, so the description must disclose behavior like whether it is read-only, what data it returns, and any side effects. It only says it 'lists' a file tree, which implies a read but doesn't explicitly confirm no mutation, rate limits, or pagination behavior. It adds minimal value beyond the name, leaving the agent uncertain about the operation's safety.

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 one sentence, efficient, and front-loaded with a clear verb and resource. It doesn't waste words. However, it could be slightly longer to include usage guidance without losing conciseness, but for what it does, it's appropriately sized.

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 no output schema and no annotations, the description must convey what the tool returns and its safety. It doesn't mention that it returns a file tree structure or any details about the output format. It also doesn't explain potential use cases like fetching a subtree vs whole repo. For a tool that could potentially return large data, this is incomplete.

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 five parameters have detailed descriptions in the schema, including defaults and examples (e.g., ref defaults to default branch, type has DIRECT/RECURSIVE/FLATTEN). The description adds nothing beyond the schema, so it provides baseline value. It doesn't clarify nuances like how path interacts with type, but the schema covers basic meaning.

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 the file tree from a Codeup repository, which is specific and action-oriented. It distinguishes it from related tools like get_file_blobs or create_file, though it doesn't explicitly mention scope or filters. The 'Code Management' prefix adds context but is minimal. Overall, it clearly states what it does.

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 gives a basic verb+resource but no explicit when-to-use guidance or alternatives. It doesn't mention when to choose this over list_commits or compare, nor does it note that it's for read-only exploration. Context is implied: you use it to see repository structure, but it lacks explicit directions for common use cases like navigating directories or specifying branches.

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