files_get

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

With no annotations, the description specifies that it returns file metadata including name, size, type, upload info, and associated entities. It doesn't mention side effects (none expected), so it's largely transparent.

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 well-structured with a main sentence followed by 'Workflow tips' and 'Common use cases' sections. Every sentence adds value without fluff.

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?

For a simple get tool, it covers purpose, return metadata, and usage context. Although no output schema exists, the description lists key return fields. Could include error handling, but not a major gap.

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% for the single required parameter 'id', which is already described as 'ID of the file to retrieve'. The description adds minimal extra meaning beyond an example usage, so baseline 3.

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 it retrieves detailed information about a specific file, including metadata like name, size, type, associated entities. This distinguishes it from siblings like files_download (downloads file content) and files_list (lists all files).

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?

Provides workflow tips such as using before downloading and checking associations, and includes common use cases. While it doesn't explicitly say when not to use, the context is sufficient for a simple get tool.

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