get_assets

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates a read-only operation ('读') and mentions '免费' (free), but does not explain what aggregation means, whether results are paginated, how images are represented, or any side effects or prerequisites. The safety profile is only partially conveyed.

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 core sentence is concise and front-loaded with the main purpose. However, the trailing sentence '免费。' is irrelevant fluff that does not earn its place, diluting the focus of an otherwise tight definition.

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 simple one-parameter tool without an output schema or annotations, the description should at least hint at the response format or aggregation structure. It lists asset categories but omits what the aggregated result looks like, whether it is grouped, and how images are returned. An agent would still have significant ambiguity after reading 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?

Schema description coverage is 0%, and the description makes no mention of the drama_id parameter or how to obtain/use it. The parameter name is self-explanatory and the schema encodes its type and constraint, but the description adds no value beyond the schema, failing to compensate for the coverage gap.

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 states a specific verb (读/read), a resource (全部资产聚合 of a drama), and enumerates the asset types covered (characters/scenes/props/images). This clearly distinguishes it from per-type getters like get_characters, get_scenes, and get_props, though the term '聚合' (aggregation) could be more explicit about what shape the data takes.

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 alternatives such as get_characters, get_scenes, get_props, or extract_assets. The description simply says it reads all aggregated assets and is 'free', without stating any selection criteria, exclusions, or related workflows.

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