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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the mutation and safety profile are known. The description adds the concrete effect ('removes the follow from the user's account'), which is useful, but says nothing about permissions, errors when no follow exists (beyond the idempotency hint), or confirmation behavior.

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?

Three short sentences, front-loaded with the trigger, then the input source, then the effect. Nothing is redundant and the ordering matches how an agent decides and then calls the tool.

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 two-parameter idempotent mutation with full annotation coverage and no output schema, the description covers trigger, inputs, and effect. The only minor gap is not stating failure behavior for a non-existent follow, though the idempotent annotation largely implies it.

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 100%, so both `key` and the `type` enum are already fully documented in the schema, and the enum constrains `type` to valid values. The description adds provenance the schema lacks — that the pair comes from `list_follows`, `find_entities`, or `get_entity` — but no format or pairing rules, so baseline 3 is appropriate.

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?

States a specific verb and resource ('stop following a drug, gene, process or other entity') and scopes it to the AgingResearch.News follow graph, which cleanly distinguishes it from the sibling `follow` and from read-only listing tools. An agent can identify the operation and its domain without opening the schema.

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?

Gives an explicit trigger ('when the user asks to stop following...') and tells the agent where the arguments come from by naming `list_follows`, `find_entities`, and `get_entity`. No when-not guidance is offered (e.g., what to do if the user was never following the entity), but the context is clear enough to act.

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