Manage third-party push categories

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

Annotations declare destructiveHint=true, so the safety profile is partly covered; the description adds the non-obvious guardrail that mutations require confirm: true, which the annotations do not express. It stops short of saying deletes are irreversible or what happens to existing categories on set.

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?

Two short clauses, front-loaded with the resource and action mapping; every element carries information. It is terse to the point of omitting needed detail, but nothing is wasted.

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 mutating tool with a nested free-form 'data' object, no output schema and zero schema descriptions, the definition says nothing about what fields belong in data, what get returns, or what delete removes. An agent could pick the right action but not construct a correct 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 coverage is 0%, so the description must compensate. It clarifies that 'set' is an upsert (新增/更新) and that confirm gates writes, but leaves the 'app' and especially the nested 'data' object entirely unexplained — a real gap for a 4-parameter tool with a free-form object.

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 resource (third-party push message category configuration) and the three operations it covers (get/set/delete). An agent can tell it's a CRUD manager for push categories, though it doesn't distinguish itself from the sibling yunxin_app_custom_push.

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 'write requires confirm: true' line gives one concrete prerequisite for set/delete, but there is no guidance on when to prefer this tool over yunxin_app_custom_push or yunxin_app_get, and no exclusions are stated.

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