mfuns_favorite

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

With no annotations provided, the description must disclose behavior itself. It explains key behaviors like list_id requirements for add/remove actions and the default list behavior. However, it does not mention what the tool returns, error conditions, idempotency, or side effects beyond the action itself, leaving some transparency gaps.

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-structured with a concise summary followed by an Args list. Every sentence provides necessary information, and there is no redundant or filler content.

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 description covers all parameters and basic behaviors, and the presence of an output schema fills return-value details. It lacks explicit usage context and interaction nuances, but for a moderately complex tool, it 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 schema has 0% description coverage, but the description compensates fully by explaining each parameter in detail: resource_id, resource_type with allowed values, action with allowed values, and list_id with default/required conditions. This adds significant meaning beyond the bare schema.

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 function as '收藏 / 取消收藏 / 查询收藏状态' (favorite/unfavorite/query favorite status), which is a specific verb+resource. It distinguishes itself from sibling tools like mfuns_react or mfuns_comment by focusing exclusively on favorite operations.

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 provides no guidance on when to use this tool versus alternatives. It explains how to perform actions (add/remove/check) but does not mention scenarios, prerequisites, or exclusions relative to sibling tools such as mfuns_browse or mfuns_react.

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