get_file_info

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

Lacks details on behavior such as error handling for nonexistent paths, symlink resolution, permissions, or return structure. With no annotations, the description should cover these traits but only lists example metadata fields.

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?

One concise sentence that front-loads the core purpose without extraneous words. Efficiently communicates the tool's function.

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?

Lacks details on output format, error responses, or behavior differences for files vs directories. While the tool is simple, a complete description would mention return type or common error cases.

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 the schema already documents parameters. The description adds no extra meaning beyond the schema's explanations of 'path' and 'workspace_root'. Baseline score of 3 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 retrieves metadata (size, modification time, type) for a file or directory, using specific verbs and resource. It distinguishes from sibling tools like read_file or list_directory by focusing on metadata rather than content or listing.

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 (e.g., list_directory for summaries, find_files for searching). The description fails to specify prerequisites, edge cases, or exclusions.

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