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

The description goes well beyond the readOnly/idempotent annotations by disclosing two critical behaviors: it does not import videos and does not call the Gumlet API, and it provides the exact dashboard path and URL. Nothing in the description contradicts the readOnlyHint=true annotation, since this is purely an advisory tool.

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?

Four short sentences, front-loaded with the purpose and followed by the mechanism, trigger condition, and exclusion. There is minor overlap between the first sentence and the 'use this when' sentence, but no sentence is wasted.

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 zero-parameter advisory tool with an output schema, the description supplies everything the agent needs: what the tool does, what it does not do, where the real importer lives, and which sibling not to substitute. Nothing is missing.

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 tool takes zero parameters, so there is no parameter meaning to add and the schema is trivially complete. The baseline for a parameterless tool applies, with no evidence warranting a higher score.

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 first sentence states a specific action and resource: it instructs the user on migrating videos from Vimeo to Gumlet. It is immediately distinguishable from siblings like create_asset or create_asset_direct_upload, and the description explicitly rules out the importer behaving like an API tool.

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?

It gives an explicit trigger ('when the user asks to import, migrate, or move videos from Vimeo') and an explicit exclusion ('Do not use create_asset as a substitute for the Vimeo importer'). It also states that import exists only in the dashboard, so the agent knows the only path is to guide the user.

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