unmute_user

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

No annotations provided. The description mentions restoring content but does not cover auth requirements, rate limits, or reversibility. For a simple undo, this is adequate but could be more transparent.

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?

A single sentence that conveys the core purpose efficiently. Could add a brief parameter note, but overall it is appropriately concise.

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 simple tool with one parameter and no output schema, the description covers the main action. Missing parameter explanation slightly reduces completeness.

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?

Single parameter 'actor' with no description in schema (0% coverage). The description does not explain what 'actor' refers to (e.g., user DID or handle), leaving ambiguity.

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 clearly states the action 'unmute', the target 'previously muted user', and the effect 'restore their content in your feeds'. It distinguishes from sibling tools like mute_user and block_user.

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 description implies usage when undoing a mute, which is appropriate for a simple toggle. It does not explicitly state prerequisites or alternatives, but the context is clear.

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