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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful scope context (app screens vs. conversation) but nothing about side effects, where the imported file lands, auth/permission needs, or any failure mode for an open-world write operation.

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 short sentences with the scope constraint front-loaded and no filler. The phrasing is fragmentary ('import_media for a file the person picked in the app') rather than a complete clause, which costs a point on structure but not on economy.

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?

An output schema exists so return values need no explanation, and the single required parameter is fully documented in the schema. Still, for a non-read-only, open-world import operation the description omits what 'import' does to the target app screen and any success/failure behavior, leaving the agent with only the negative scoping rule.

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 description coverage is 100% and the nested file object documents file_id, file_name, mime_type and download_url individually, so the schema carries the burden. The description adds no parameter-level meaning beyond that, making the baseline 3 correct.

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 scopes the tool precisely ('For the Veltake app's own screens only') and explicitly separates it from conversation-context imports and from the sibling import_media. However, it never actually states the action — the verb 'import' and the resource 'attached file' live only in the name/title, so the description alone reads as a constraint rather than a purpose statement.

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 negative rule ('not for a conversation') and names the alternative to use instead ('import_media for a file the person picked in the app'), which is real routing guidance. The alternative clause is telegraphic and slightly ambiguous about which tool handles person-picked files, so it falls short of a fully unambiguous when/when-not pair.

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