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

Goes well beyond the annotations: login required, idempotent, the other party is not notified, 404 semantics and a do-not-retry rule, and the boundary that this does not affect future icebreaker messages. The idempotent/not-destructive annotations are reinforced with concrete failure-handling guidance.

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?

Very dense and front-loaded with the login prerequisite, and every clause carries information. However, the telegraphic style packs several ideas per clause (e.g. '仅此会话,不改未来破冰'), which is slightly harder to parse than a plainly structured sentence.

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 two-parameter mutation with no output schema, it covers preconditions, idempotency, side effects, error handling, scope limits, and the sibling tool to use instead. Nothing an agent needs to invoke it correctly is missing.

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 both conversationId and muted are already documented, and the baseline is 3. The description does add sourcing information for conversationId (from list_my_conversations, id or activityId), but says nothing extra about the muted toggle beyond what the schema states.

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 and resource (mute a conversation) with explicit scope: the caller's own DM or group, only that one conversation. An agent can distinguish it from set_notification_prefs and set_moment_mute without opening a schema.

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 an explicit prerequisite workflow (get the id/activityId from list_my_conversations, then set) and names the alternative for the other case: use set_notification_prefs for global push settings. It also states when not to retry (404 = no access or already left).

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