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

Annotations only flag it as a non-read-only, non-idempotent, non-destructive write. The description goes well beyond that with masking, background pause, 8 MB per-visit cap, 1 GB per-workspace quota, 30-day retention, future-visits-only scope, and precedence rules – exactly the operational context an agent needs before mutating this setting.

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?

Front-loads the core action, then packs the behavioral constraints into a dense but purposeful block. Nearly every clause carries a concrete limit or precedence rule, though the middle sentence is heavy enough to require careful parsing.

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?

No output schema and no return-value expectations needed for a boolean toggle, and the behavioral picture is thorough. The gap is parameter identification, but otherwise an agent has enough to invoke and reason about the effect.

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 0% and neither parameter is named or explained. The description never clarifies that 'on' is the boolean toggle and 'proposal_id' identifies the target page/link, so an agent must reverse-engineer both from the schema alone.

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 pair (enable/disable) and resource (HTML session recording for this page's link and folder visits). The clause about the workspace-wide off switch implicitly distinguishes it from the sibling set_replay_settings, but it never names that alternative, so the differentiation is inferential rather than explicit.

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?

Conveys context (default on, opt-outs persist, workspace switch overrides), which helps an agent understand the setting's behavior, but gives no explicit when-to-use vs set_replay_settings or get_replay_settings, and no prerequisites for calling it.

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