job_alert_list

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds value by detailing the output includes pagination info, a summary of the underlying job search, and a system_instruction for presenting results, which goes beyond simple read-only semantics.

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 well-structured with clear Input/Output sections, each sentence providing essential information without redundancy. It is appropriately sized and leaves no unnecessary words.

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?

Given the simple parameter set (3 optional params, no nested objects), the presence of an output schema, and annotations, the description sufficiently covers the tool's behavior. It even mentions the system_instruction and summary info, making it complete for an agent to use effectively.

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 description's Input section merely restates the parameter names, defaults, and ranges already present in the schema. The description adds no extra semantic value beyond what the schema provides, so the baseline of 3 applies.

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 lists the authenticated user's job alerts across all subscription sources, using a specific verb (Lists) and resource (job alerts). It distinguishes itself from sibling tools like job_alert_unsubscribe by focusing on read-only listing.

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 implies usage context by specifying it returns alerts for the authenticated user and covers all subscription sources, but it does not explicitly mention when to choose this over alternatives like job_alert_unsubscribe. There are no exclusions, but no explicit alternative guidance is provided.

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