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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the mutation/idempotency profile is covered. The description adds genuinely new behavioral context: the event is delivered to a private Live 'org' channel, it fires on change, risk appearance or server outage, and an org key is required.

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, front-loaded with the core action and outcome, then the quota/key constraints. Dense but every clause carries information; only the plan-tier numbers are arguably secondary.

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 mutation tool with no output schema, the description covers the side effect (pinning), the trigger conditions and the delivery channel, and annotations cover the safety profile. It stops short of describing the returned subscription/event payload or how to tear the watch down, which 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 description coverage is 100%, so the schema already documents both `server` and `repin` with defaults. The description's "pin the current tools as approved" gestures at repin but adds no syntax, format or interaction detail beyond the schema, so baseline 3 applies.

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 states a specific verb and resource: pin the server's current tools as approved and receive real-time change/risk/downtime events. It is clearly distinguishable from scan_changes, scan_rescan and scan_server by its watch-and-alert framing, though it never names the sibling it complements (scan_unwatch) to close the loop.

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 gives real prerequisites ("Needs the org key") and quota context (Free plan 3 servers, Pro 500), which helps an agent decide feasibility. However, it never says when to choose this over scan_unwatch, scan_watchlist or scan_changes, so the selection guidance is only implied.

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