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

Annotations already cover idempotency and non-destructiveness, and the description adds beyond them: other follow settings are untouched, and there is a pending state where old unread counts may change — a real side effect disclosed up front. It leaves minor gaps (whether the old filter set is lost immediately or after pending completes), so not 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?

Four short sentences with the core replace semantics front-loaded, then scope, then the empty-filter shorthand, then the pending side effect. No sentence is redundant and nothing important is buried.

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?

With annotations, an output schema and full parameter coverage already present, the description only needs to carry the non-structured behavior, and it does: replacement semantics, unaffected settings, and pending/unread consequences. A small gap remains around preconditions (does the follow need to be active or unpaused).

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% and the schema itself carries the detailed semantics (OR groups vs AND fields, remote tri-state, market slugs, compensation units). The description only repeats the [{}] shorthand and the complete-set-not-patch point already stated in the filters description, so it adds little at the parameter level.

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?

'Replace all match filters for a followed company' gives a specific verb (replace), resource (match filters) and scope (followed company), and the replace-not-patch framing separates it from incremental update tools. It never names a sibling as an alternative, so it stops short of full differentiation.

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?

It clarifies usage for the edge case 'Pass [{}] for all new openings', which is genuinely useful. However there is no explicit when-to-use / when-not guidance relative to siblings such as following.follow, following.pause or following.digest.update, so selection context is only implied.

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