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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the pin is released, developments stop getting a dedicated entry, and it succeeds even when the originating briefing no longer exists. It does not discuss reversibility or re-following, which keeps it from a 5.

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, both front-loaded: the action and its effect come first, the edge-case justification second. No filler, no restatement of the title.

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 one-parameter, single-object mutation with an idempotency annotation and no output schema, the description covers the action, the effect, the id source, and the key edge case that separates it from its sibling. Nothing an agent needs to call it correctly is missing.

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%, so the baseline is 3, but the description adds provenance value by telling the agent exactly where to obtain story_id (get_information_diet → followed_stories), matching the schema's own hint. It adds no format details, so it stays below 5.

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 (release/unfollow) and resource (pinned story) and immediately names the source of the id, get_information_diet → followed_stories. It also distinguishes itself from the similar sibling rate_briefing_entry "unfollow", so an agent can pick between them without opening either 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?

Explicitly names the alternative (rate_briefing_entry with the "unfollow" argument) and the condition that selects this tool over it: the briefing may already be gone, since this path does not require the briefing. That is a concrete when-to-use rule rather than implied context.

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