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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so safety is covered. The description adds genuinely useful context — no AI processing is triggered and a seq is returned — but leaves open the obvious consequence of idempotentHint=false: what happens when the same URL is imported twice.

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, front-loaded with the core action and sources, with the important caveat last. Nothing is redundant or padded.

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 two-parameter import tool with full schema coverage and annotations, the description covers sources, scope, return value and the non-triggering of AI processing. Only the duplicate/re-import behavior 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?

Schema description coverage is 100%, so both url and private are fully documented in the schema; the description only restates the accepted URL types. Baseline 3 applies since the schema already does the semantic work.

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 (import) and resource (a single episode), enumerates the three accepted URL sources, and names the return value (its seq). The closing clause 'Importing does not start AI processing' separates it from the process_episode sibling without either schema being opened.

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?

The 'does not start AI processing' note strongly implies the follow-up path (process_episode), but no sibling is named and no explicit when-to-use/when-not guidance or prerequisites are given. Usage is implied rather than stated.

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