get_media_details

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

No annotations are provided, so the description carries the burden. It only states a return of '媒体详细信息' (media details) without disclosing any behavioral traits, such as how title/year are used, error handling, or required permissions. The lack of safety or side-effect information is notable.

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?

The description is concise and well-structured: a one-line summary, a bullet-like list of args, and a one-line return statement. It is easy to parse and does not contain unnecessary verbiage, though it could benefit from richer details without harming conciseness.

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?

With no output schema and no behavioral annotations, the description leaves the return format, potential errors, and the role of optional parameters (title, year) unexplained. For a tool with five parameters, this is insufficient context for an agent to reliably use it.

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?

The input schema has 0% description coverage, so the description must compensate. It lists parameter names with brief Chinese labels, but these largely mirror the schema (e.g., enums for id_type and media_type). No additional meaning is provided about parameter formats, relationships, or validation rules, leaving gaps for the agent.

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 clearly states the tool retrieves media details ('获取媒体详细信息'), with a specific verb and resource. It differentiates from siblings like search_media_or_person and discover_* tools by focusing on detail lookup, though it doesn't explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus other related tools. It simply lists parameters and a return value, leaving the agent to infer that it is for fetching details by known IDs.

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