list_files

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

With no annotations, the description does a good job explaining what the tool does (read-only listing). It does not mention side effects, permissions, or performance, but for a simple list operation these may not be required. The description is transparent about the scope (BASE_DIR files and other ingested items).

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 two sentences, front-loaded with the primary action, and no wasted words. Every sentence adds distinct information.

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?

Given no parameters and no output schema, the description provides sufficient context for an agent to decide when to call this tool. It covers the tool's scope (files and other ingested items) but does not specify return format or pagination. Still, it is complete enough for a straightforward list tool.

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?

There are zero parameters, so the schema coverage is trivially high (100%). The description adds value by explaining what is listed, which goes beyond the empty schema. Baseline 4 is appropriate.

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 files in BASE_DIR with specific extensions and shows ingestion status. It also lists other ingested items outside BASE_DIR. This is a specific verb (list) and resource (files and ingested items), distinguishing it from siblings like delete_file or ingest_file.

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 provides context for when to use (checking files and ingestion status) but does not explicitly state when not to use or mention sibling alternatives. It lacks exclusions or comparisons, so the agent must infer usage boundaries.

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