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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful scope beyond that: 'Only public catalog metadata is returned, never playable video,' which sets a real expectation about what is and isn't obtainable. It stops short of describing failure modes for invalid ids or URL handling 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?

Three sentences with no filler: the payload description first, then id sourcing, then the metadata-only caveat. The long field enumeration in sentence one is dense but purposeful. Minor redundancy with the output schema, which likely already lists these fields.

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?

Single required parameter, full schema coverage, an output schema, and clear read-only annotations — the description covers everything an agent needs: what it returns, how to obtain the id, and that video is out of scope. Nothing material is missing for correct invocation.

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% and the schema already documents that id is digits or a dramabox.com drama URL. The description reinforces provenance ('Get title ids from dramabox_browse, dramabox_more or dramabox_home'), which helps an agent source the value correctly, adding modest value over the schema's 'from any DramaBox list' phrasing.

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 ('Get one DramaBox short drama') and then enumerates exactly what comes back: title, cover, language, episode count, views, tags, genres, per-episode number/duration/free flag, and related titles. That detail cleanly separates it from the list-oriented siblings (dramabox_browse, dramabox_home, dramabox_more, dramabox_genres), which return collections rather than a single title.

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 precondition for the id parameter by naming the three sibling tools that produce ids (dramabox_browse, dramabox_more, dramabox_home). It does not spell out a negative case or say what to do if the id is unknown, but the upstream-tool routing is unambiguous enough that an agent knows the sequence.

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