get_subscribe

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

No annotations are provided, so the description carries the full burden of disclosure. It discloses the return value (subscription details or None if not found) and the conditional behavior of the season parameter. It does not explicitly state read-only nature, potential side effects, or authentication requirements, but for a retrieval operation this is acceptable.

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, with distinct Args and Returns sections. Every sentence adds value without redundancy, making it easy for an agent to parse and extract key 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 straightforward get tool, the description covers: purpose, query modes, parameter semantics, and return behavior including the None case. It does not mention explicit integration with sibling tools or provide examples, but the tool's simplicity means the description is largely complete.

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 Args section thoroughly explains all three parameters, including the enum values for id_type, the meaning of id_value, and the conditional relevance of season. Since the input schema has no property descriptions (0% coverage), this fully compensates for the schema's lack of semantic detail.

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 '获取订阅信息' (get subscription information) and specifies querying by subscribe ID or media ID (tmdb/douban), indicating a concrete resource and action. However, it does not explicitly distinguish this from sibling tools like get_media_details, though the subject (subscriptions) is distinct.

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 implies the tool is for retrieving subscription records and provides parameter-level guidance (e.g., season is only valid for tmdb/douban). It does not explicitly mention when to use this tool versus alternatives such as list_subscribes or get_media_details, so the usage context is inferred rather than stated.

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