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

With no annotations, the description carries the burden but does state 'Read-only' and explains the server-default fallback when activity_id is omitted. However, it omits whether the conversion is idempotent, whether the link expires, and any auth/permission requirements for the yuantoutao console ID.

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?

Compact and front-loaded, leading with the platform and action. Some internal jargon ('LBS business — no product shelf') is terse, but every clause adds routing or default-handling 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 single-parameter, no-output-schema tool, the description covers the purpose, the calling scenario, and the default-ID behavior; the implied return (an affiliate link) is derivable from the stated conversion. Minor gaps around link lifetime/expiry remain.

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 coverage is 100% (baseline 3), and the description adds meaning beyond the schema by naming what the server default actually is ('Taobao 领券中心 eleme activity') and reinforcing the omission behavior.

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?

States a specific verb (convert) and resource (official ele.me activity: red-packet/landing page) into a defined output (our affiliate link). The sibling converters (cps_jd_convert, cps_pdd_convert) are clearly distinguished by platform.

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?

Gives clear context: 'LBS business — no product shelf; give the link to users who want food delivery.' This tells the agent the scenario in which this tool applies and, implicitly, that shelf/search tools are inappropriate. It does not explicitly name an alternative or state exclusions, so it stops short of 5.

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