Files_Listallfiles

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It merely states 'List all files' without addressing pagination, rate limits, order, or what the response contains. This provides almost no behavioral insight.

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 extremely short (three words), which is efficient but sacrifices critical information. It is front-loaded (the purpose is clear), but it fails to include any additional context that would help an agent, making it borderline under-specified.

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 the tool's simplicity (0 params, no output schema), the description could still be more complete by hinting at scope, pagination, or result format. Without such information, the agent may misinterpret the tool's behavior.

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 input schema has zero parameters and 100% coverage, so the schema already fully describes the absence of parameters. Per the rubric, 0 parameters yields a baseline of 4. The description adds no extra meaning, but none is needed.

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 'List all files,' using a specific verb and resource. However, it does not differentiate from sibling tools like 'Files_Retrieveafile' or other list tools (e.g., 'Products_Listallproducts'), missing scope or context.

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 guidance on when to use this tool versus alternatives like 'Files_Retrieveafile' or other list operations. There is no mention of prerequisites, filtering, or whether it lists all files across the entire system or within a specific context.

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