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

The description does not contradict the 'readOnlyHint' annotation. It adds minimal behavioral context beyond stating it gets metadata. With the annotation present, the description is sufficient but does not disclose additional traits like rate limits or authentication needs.

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 concise sentences: the first states the purpose, the second provides the REST API endpoint. No unnecessary words, and both sentences are informative.

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 read-only tool with one required parameter and annotations present, the description adequately covers what the tool does. It does not explain return format, but no output schema exists, so the added detail is sufficient.

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?

The only parameter 'uuid' is described in the schema as 'File UUID.' The description does not add meaning beyond that. With 100% schema coverage, 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 verb 'get' and the resource 'file metadata', and specifies it returns 'all custom metadata key/value pairs for a file'. This distinguishes it from sibling tools like 'uploadcare_get_file' which retrieves file details.

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 explicit guidance on when to use this tool versus alternatives. The purpose is clear from context, but there is no statement like 'use this to retrieve only custom metadata' or 'do not use to get file properties'.

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