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

Annotations declare the safety profile (not read-only, not idempotent, not destructive, closed-world), so the description need not repeat that. It adds genuinely new behavior: the tool opens an interactive panel requiring user interaction with a drop zone/chooser, which is critical to know before invoking. It does not cover failure modes or what happens if the upload is cancelled.

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, no filler. The interactive-panel mechanic and the file-type scope come first, and the routing rule to pick_media is placed last as a natural contrast. Every clause carries information.

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 single-parameter, no-output-schema tool, the description covers the interaction model, supported file types, and sibling routing. The remaining gap is that it says nothing about what happens after upload (return value, failure/cancel behavior), which matters since no output schema exists.

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?

Only one parameter, and the schema already documents it fully at 100% coverage, including the uuid format and the warning not to abbreviate or reconstruct it. The description adds only 'the given draft,' which is redundant. Baseline 3 applies when the schema does the heavy lifting.

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 ('uploaded to Taplio and attached to the given draft in one step'), names the accepted file types (image, video, PDF), and explicitly distinguishes itself from the sibling pick_media. An agent can tell this apart from attach_media_from_url and pick_media without opening any 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 an explicit selection rule — 'Use whenever the file is not in the library yet' — and names the alternative ('to reuse an existing asset instead, call pick_media'). The when-to-use and when-not-to-use conditions are both stated.

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