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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the critical behavioral constraint that user confirmation is required before the bulk action executes, which is not explicit in the annotations. It does not repeat what annotations already state, adding value without redundancy.

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?

A single, efficient sentence that leads with the core function and then states the condition. No filler or wasted words, and the most important information is front-loaded.

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 simple one-parameter tool with an output schema and comprehensive annotations, the description covers every essential aspect: what it does, the condition for use, and the scope. The bulk vs. singular distinction is implied by the wording, and the confirmation requirement is explicit. Nothing an agent needs to invoke 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?

With 100% schema description coverage, the single parameter 'confirmed' is already fully documented in the schema ('Must be true after the user confirms marking all openings read'). The tool description's phrase 'after the user confirms the bulk action' essentially repeats this same semantics, adding no new meaning beyond the schema. 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?

The description clearly states the action (mark as read), the exact scope (every unread opening notification), and the prerequisite (user confirmation). It distinguishes itself from sibling signals.openings.mark_read by emphasizing the bulk nature ('every unread', 'bulk action'), leaving no ambiguity about what it does.

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?

The description specifies the condition for use: only after user confirmation. It does not explicitly name alternatives like signals.openings.mark_read for single notifications, but the wording 'every unread' and 'bulk action' strongly conveys that this is for bulk operations. It lacks an explicit exclusion clause, so it stops short of a perfect 5.

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