bsky_remove_from_list

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions authentication requirement ('要認証'), which is valuable context. However, it doesn't describe what happens after removal (e.g., whether it's reversible, confirmation messages, error conditions), rate limits, or permission requirements beyond authentication. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 sentence that states the core action and key constraint (authentication). No wasted words or redundant information. However, it could be more front-loaded by explicitly mentioning the tool removes list items rather than just 'users from lists'.

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 this is a mutation tool with no annotations, 2 parameters (0% schema coverage), but with an output schema present, the description is moderately complete. The authentication requirement is helpful, but missing details about parameter meanings, behavioral outcomes, and error conditions leave gaps. The output schema existence means return values documentation isn't needed in the description.

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 for undocumented parameters. The description mentions 'ユーザーをリストから' (user from list) which partially explains the purpose of 'listitem_uri' but doesn't clarify parameter meanings, formats, or relationships. No information about 'acting_handle' parameter is provided. The description adds minimal value beyond what's implied by the tool name.

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 ('削除します' - remove) and target resource ('ユーザーをリストから' - user from list), which is specific and unambiguous. It distinguishes from siblings like 'bsky_add_to_list' by specifying removal rather than addition. However, it doesn't explicitly mention what 'listitem_uri' represents, leaving some ambiguity about the exact resource being manipulated.

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 context through the authentication requirement ('要認証'), suggesting this tool requires authenticated access. However, it doesn't explicitly state when to use this versus alternatives like 'bsky_delete_list' (which deletes entire lists) or 'bsky_unfollow' (which handles different relationships). No explicit guidance on prerequisites or exclusions is provided.

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