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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the sort order (most recent first), the fields returned, and the optional filtering 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?

Two sentences, zero padding. What the tool returns and its ordering come first, then the actionable usage guidance. Every clause earns its place.

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 read-only, zero-required-param list tool with full schema coverage, an output schema, and annotations covering safety, nothing is missing. The description supplies the ordering and workflow routing that structured fields cannot.

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 the baseline is 3. The description restates the query semantics ('filter by a filename substring') and omits limit entirely, adding no syntax or behavior beyond what the schema already documents.

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?

Specific verb (List) plus resource (media you've already uploaded to Taplio), and it enumerates the returned shape (id, type, public url, filename) and ordering (most recent first). It implicitly separates itself from upload_media/create_media_upload_url by stressing 'already uploaded', though it never explicitly distinguishes itself from pick_media.

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?

Clear workflow context: 'Use it before drafting so you can attach existing media via create_draft or update_draft media_ids — no re-upload needed.' That routes the agent to this tool instead of re-uploading. No explicit when-not or named alternative tool, but the intent is unambiguous.

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