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

Annotations only cover idempotency and non-destructiveness, so the description carries real weight here: it discloses the login prerequisite, that the muted user receives no notification, that their profile page remains visible, and that the effect is reversible. The one gap is that it doesn't state what the call returns on success, which matters less because there is no output schema.

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?

One compact sentence-chain with three front-loaded clauses: login requirement, then the two parameter states, then alternatives. Every clause earns its place; nothing is repeated from the schema verbatim and no filler is present.

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 2-parameter boolean toggle with no output schema and thin annotations, the description supplies everything an agent needs: auth requirement, exact effect of each value, reversibility, notification behavior, and neighboring tools. No meaningful gap remains.

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%, so the baseline is 3; the description still adds context beyond the schema strings by explaining what muted=true actually does in the feed and what the muted user will and won't notice. This goes beyond the schema's 'true 不看 TA' and justifies one point above baseline.

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 the specific operation precisely: setting muted=true removes the target user's posts from 'my moment feed', and muted=false restores them. It also explicitly separates itself from block_user ('想彻底断开用 block_user'), so an agent can distinguish it from the closest sibling without inspecting schemas.

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 explicit when-to-use (hide a person's feed posts), when-not (if you only dislike one post, '直接跳过即可'), and the alternative for a stronger action (block_user for full disconnection). This is a complete routing table for the decision an agent actually faces.

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