persons_delete_follower

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

The description explains the effects of removal in detail: no more notifications, but access remains if permissions allow. It clarifies that only notification settings are affected, not access rights. No annotations provided, so the description fully carries the transparency burden.

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 well-structured with a clear one-line summary at the start, followed by detailed bullet points of effects and use cases. Every sentence adds value, and the note about follower_id is appropriately placed.

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?

The description covers the tool's purpose, effects, and use cases. However, it does not explicitly mention whether the deletion is reversible (i.e., if a follower can be re-added later). Given the lack of output schema, this is a minor gap.

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%, and the description adds value by clarifying that follower_id is the user ID of the follower to remove, which is not explicitly stated in the schema description (only 'User ID of the follower to remove'). This adds useful context beyond the schema.

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 'Delete a follower from a person,' which is a specific verb-resource pair. It distinguishes the tool from siblings like persons_add_follower and persons_list_followers.

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 lists specific use cases: managing notification preferences, adjusting team involvement, reducing notification noise, changing account ownership responsibilities. It does not explicitly state when not to use it, but the context implies it's for removing followers.

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