Unsubscribe from all job alerts

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely new context: the confirm guard's rejection behavior and the explicit idempotency claim ('returns success even when the user has no active alerts') plus the source coverage.

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-loaded purpose sentence followed by tight Input/Output sections. Every sentence carries distinct information with no redundancy.

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 single-parameter bulk mutation, the description covers the confirm requirement, the safety rationale, source scope, and idempotency, while the output schema carries the return value. Nothing needed to call 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?

Schema coverage is 100% and the single parameter is documented there, so baseline is 3. The description adds the rationale behind the guard ('guards against an unintended bulk unsubscribe'), giving the agent the meaning of the flag beyond its schema text.

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?

Specific verb + resource + scope: 'Unsubscribes the authenticated user from ALL of their job alerts at once, across every subscription source.' It clearly distinguishes itself from the singular sibling job_alert_unsubscribe by emphasizing the bulk/all scope.

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 'ALL ... at once' framing implicitly routes the agent away from the single-alert sibling, and it enumerates the subscription sources covered. However, it never explicitly names job_alert_unsubscribe as the alternative for single-alert cases, so exclusion guidance is inferential.

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