bsky_mute

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

With no annotations provided, the description carries full burden but only mentions authentication requirement. It doesn't disclose what muting entails (e.g., hides posts from timeline, is reversible via 'bsky_unmute', doesn't notify user), rate limits, or error conditions. The authentication note is helpful but insufficient for a mutation tool.

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?

The description is a single, efficient Japanese sentence that states the core purpose upfront. No wasted words, though it could benefit from slightly more detail given the tool's complexity.

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 mutation tool with 2 parameters, 0% schema coverage, no annotations, but with an output schema present, the description is minimally adequate. The authentication note is helpful, but more behavioral context and parameter explanation would improve completeness given the tool's social media impact.

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 description coverage is 0%, so the description must compensate but provides no parameter information. It doesn't explain what 'handle' represents (user identifier) or what 'acting_handle' is for (optional override of authenticated user). Two parameters remain completely undocumented.

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 ('ミュートします' - mutes) and target ('指定ユーザー' - specified user), providing a specific verb+resource. However, it doesn't explicitly differentiate from sibling tools like 'bsky_block' or 'bsky_unmute' beyond the basic action name.

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 only mentions authentication requirement ('要認証'), but provides no guidance on when to use this tool versus alternatives like 'bsky_block' or 'bsky_unfollow', nor any context about when muting is appropriate versus other actions.

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