job_alert_unsubscribe_all

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

The description adds significant behavioral context beyond annotations: the confirm parameter must be true (with rejection otherwise), it reports the number unsubscribed, and it is idempotent (returns success even with no active alerts). This complements the idempotentHint and destructiveHint annotations without contradicting them.

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?

The description is concise and well-structured: a clear purpose sentence, then Input/Output sections, and an idempotency note. Every sentence adds useful information with no wasted words or repetition of structured fields.

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?

The tool is simple (one parameter) and the description covers what it does, the confirmation guard, the output behavior, and idempotency. With annotations and an output schema present, the description is complete enough for an agent to use the tool correctly without further context.

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% for the single parameter, so the schema already documents the confirmation requirement. The description repeats this and adds the rationale about guarding against unintended bulk unsubscribe, but this is marginal extra value. The baseline of 3 is appropriate when the schema carries the parameter details.

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 tool unsubscribes the authenticated user from ALL job alerts across every subscription source (regular, company page, MCP). It uses a specific verb+resource+scope and inherently distinguishes itself from the sibling 'job_alert_unsubscribe' by emphasizing 'ALL' and 'at once'.

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 indicates this is a bulk operation for all alerts, implying it should be used when the intent is to unsubscribe from everything at once. It does not explicitly name alternatives or state when not to use it, but the scope is clear enough that an agent would not confuse it with a single-alert unsubscribe.

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