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

Annotations already declare this is a non-read-only, open-world write. The description adds value beyond them: it discloses that the domain is re-resolved on this call, that no credits are consumed, and that the result is an Asset ID. It does not address re-import behavior or error cases, but the added operational facts are meaningful.

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?

Six short fragments, front-loaded with the action and resource before the workflow and cost notes. Every sentence carries information, though the staccato style slightly fragments the related constraints.

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?

No output schema exists, and the description compensates by naming the return value (Asset ID) and the follow-up tool (patch_film). For a three-parameter mutation this is nearly complete; only failure/duplicate behavior is left unspecified.

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%, so the baseline is 3, but the description adds real semantic coupling: 'the same domain' must match search_logo, and ids must come from that search. It adds meaning beyond the schema text without restating projectId, which the schema already explains.

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 and resource ('Import one logo ... as an image asset') and names the source tool (search_logo) and destination mechanism (patch_film). An agent can distinguish it from import_asset_url, import_gif, and add_from_library without opening a schema.

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?

Gives clear workflow context: pull domain and logoId from search_logo, don't invent ids, place the result with patch_film. It stops short of explicitly excluding the adjacent import_* siblings, but the sourcing constraint makes the intended path unambiguous.

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