search_album

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

The description discloses that the tool returns a dictionary with albums, total_count, and an optional error field when order_by or time_range are invalid. However, it does not mention whether the operation is read-only or highlight any side effects, though the search nature implies read-only 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?

The description is well-organized with a brief intro followed by a bulleted parameter list, making it easy to parse. While it is slightly verbose in repeating default values and explanations, it remains focused and avoids unnecessary fluff.

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?

The return structure is described at a high level (albums, total_count, error) and the error condition is specified. Although the detailed shape of each album item is not included, that information is likely provided by related tools (e.g., browse_albums or get_album_detail), so the description is sufficiently complete for the tool's scope.

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?

Every parameter is explained with specific meaning and allowed values. For example, keyword is described as supporting album ID, title, author, and tags, and order_by and time_range each have explicit value lists with Chinese descriptions. This adds substantial semantic detail beyond the bare schema types and defaults.

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's purpose: '搜索本子' (search albums), and it explicitly mentions supporting advanced filter options. The verb 'search' distinguishes it from sibling tools like browse_albums or get_album_detail, making the action and resource unambiguous.

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?

The description does not explicitly state when to use this tool versus the sibling tools, such as browse_albums or get_album_detail. No conditions or alternative scenarios are mentioned, leaving the agent to infer usage context from the parameter list alone.

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