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

Annotations already state this is a non-read-only, non-destructive, non-idempotent mutation. Beyond that, the description adds genuinely new behavioral facts: file preparation is free, rate limits (3 starts per email per 30 days, 20 starts per UTC day) apply, and overflow requests are queued rather than rejected, and the call returns a queued publication plus the target version. It does not say what happens on error or whether request_id is the retry/dedup key, despite idempotentHint=false.

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 English portion is two well-formed sentences that lead with the action and then the limits. However, the entire description is duplicated verbatim in Chinese, roughly doubling length without adding information for a single-language reader, and the rate-limit sentence is dense while the request_id semantics remain unstated.

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 3-required-parameter mutation with no output schema, the description covers return shape and rate-limit behavior well. It remains incomplete on the semantics of request_id, on how material order or duplicates are handled within materials, and on failure modes — gaps that matter for an agent composing a valid, retry-safe call.

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%, so the description must carry parameter meaning. It names all three parameters and explains that materials accepts either text or already-uploaded document references, which is useful. But it gives no meaning for request_id (its role as a caller-supplied key) and no guidance on the text/document union or the document_id format beyond what the schema already enforces.

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 gives a specific verb and resource ("Add text or uploaded documents in materials to order_pack_id") plus the return value ("queued material publication and its target version"). It does not, however, distinguish this from the sibling add_compliance_material, which an agent could easily confuse with it; the only differentiator is the parenthetical "成员侧" (member-side).

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?

Usage is implied rather than stated: the agent can infer that this is the member-side material add and that materials may be text or already-uploaded documents (implying start_document_upload must run first). There is no explicit when-to-use versus add_compliance_material or a clear precondition statement, but the mention of free file preparation and the queueing rules gives useful operational context.

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