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

Annotations declare readOnlyHint=true, so the safe-read profile is established. The description adds that it returns custom metadata key/value pairs, but doesn't mention permissions, whether metadata can be empty, or error behavior.

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?

Single sentence stating purpose plus REST endpoint, front-loaded and waste-free.

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?

Basic retrieval tool with no output schema. The description covers what it gets but lacks detail on return structure (key/value map) or edge cases; adequate but not rich.

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?

One parameter (uuid) with 100% schema description coverage; the schema fully documents it. The description correctly implies the uuid identifies the file but adds no syntax detail beyond schema, capping at 4.

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?

States a specific verb (Get) and resource (custom metadata key/value pairs for a file), clearly distinguishing it from siblings like uploadcare_get_file (file info) and uploadcare_list_files (file 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 vs uploadcare_get_file or other retrieval tools. The REST endpoint is provided but no context about when metadata retrieval is appropriate.

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