top_files

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

The description discloses that optional filters exist for size, age, and glob patterns, which is a behavioral trait beyond the schema. However, it does not mention whether the operation is read-only, output format, sorting order, or potential performance impacts. With no annotations, more detail would be expected.

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 a single, front-loaded sentence with no extraneous words. It efficiently conveys the core purpose and key filter capabilities.

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 has 9 parameters, no output schema, and no annotations, this description is incomplete. It does not explain return values, sorting order, default behavior, or practical usage context, leaving the agent with many unresolved questions.

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?

With 0% schema description coverage, the description must compensate for parameter explanation. It references size, age, and glob include/exclude, which maps to several parameters, but completely omits limit, maxDepth, maxFiles, and rootPath. The high-level categories help but leave significant gaps.

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 identifies the resource as files and the intent to show the largest ones, differentiating it from sibling tools like top_dirs by specifying files. However, it lacks an explicit verb such as 'list' or 'show', making the purpose slightly implicit.

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 no guidance on when to use this tool versus alternatives like top_dirs or scan_summary. It only implies usage through its filter options, but does not state prerequisites, exclusions, or alternative recommendations.

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