job_alert_subscribe

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

The description expands on the idempotentHint annotation by explaining that an existing subscription is updated without duplication. It also states the output shape (id, status, frequency) and notes the auth requirement. No contradiction with annotations.

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 compact and well-structured with Input/Output sections. Each sentence contributes value, and it is appropriately sized for the tool's complexity.

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?

With an output schema present and annotations covering safety and idempotency, the description provides output details and behavioral context. It is sufficiently complete for a simple two-parameter tool.

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?

The input schema already covers 100% of parameters with equivalent descriptions, including accepted formats and default for frequency. The description repeats these details without adding significant new semantics beyond the schema.

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 opens with 'Subscribes the authenticated user to job alerts for a specific saved job search,' using a specific verb and resource. This clearly distinguishes the tool from siblings like job_alert_unsubscribe and job_alert_list.

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 provides context such as being for an authenticated user, targeting a saved job search, and being idempotent. However, it does not explicitly compare with sibling tools or state when not to use it, making usage guidance implied rather than explicit.

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