unmute_user

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

Discloses rate limiting and risk scanning behavior beyond the schema, which is valuable. But with no annotations provided, the description carries the full burden; it omits other behavioral traits like reversibility or permissions.

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 sentences with no fluff: first sentence states purpose, second adds crucial context. Well front-loaded and efficient.

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?

Given the simplicity of the action and presence of output schema, the description covers purpose, parameter details, and important rate-limit behavior fully.

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?

Clarifies the screen_name parameter format (without @), adding essential meaning beyond the schema's type and title. Parameter is simple but comprehensively explained.

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?

Clearly states the action (unmute) and resource (user) with the specific input (screen name). Distinct 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?

Explicitly warns against bulk usage due to rate limiting and risk scanning, providing clear usage context. However, does not explicitly contrast with alternatives beyond the sibling list.

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