Get File Info

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

Annotations declare readOnlyHint, making the read-only nature explicit. Description adds value by listing specific metadata fields and mentioning allowed-directory restrictions, which are beyond annotation scope.

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?

Two sentences efficiently cover purpose, details, and constraint. No redundant or vague wording. Information is front-loaded.

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?

Tool has one parameter and an output schema. Description covers essential aspects: what it retrieves, its read-only nature, and directory restriction. Could mention error handling for missing files, but output schema likely covers return structure.

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?

Only parameter 'path' has no schema description (0% coverage). Description implies its purpose (path to file/directory) but does not add format or validation details. With only one simple parameter, this is adequate but not exceptional.

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?

Description clearly states verb (retrieve) and resource (file/directory metadata). It distinguishes from siblings by noting it does not read content, contrasting with read_file. Lists specific metadata fields (size, times, permissions, type).

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?

Description indicates when to use: 'perfect for understanding file characteristics without reading the actual content'. Constraint 'Only works within allowed directories' provides context. Explicit alternatives not named, but usage context is clear.

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