get-file-info

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

The description uses 'detailed information' but does not specify what fields or properties are returned (e.g., size, type, permissions). No annotations are provided, so the description carries the full burden. It omits important behavioral traits like whether it is read-only or requires permissions.

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, concise sentence. It is appropriately sized for a simple tool but lacks structure like bullet points or explicit formatting. It is front-loaded with the core action.

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 absence of an output schema, the description should explain what 'detailed information' includes. It does not, leaving uncertainty about return values. This is a notable gap for a tool with one parameter and no output schema.

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 coverage is 100% with one parameter ('path') described as 'Path to the file or directory'. The description adds no extra meaning beyond the schema. Baseline 3 is appropriate as the schema does the work, but the description adds no additional value.

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 'Get detailed information about a file or directory', which is a specific verb and resource. It distinguishes from sibling tools like list-directory (which lists contents) and search-files (which finds files) by focusing on detailed info of a single item, though it does not explicitly differentiate.

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. It does not mention exclusions, prerequisites, or context that would help an agent decide between this and similar tools like get-system-info or check-disk-space.

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