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

No annotations are provided, so the description carries full burden. It clearly states that the tool returns upcoming scheduled jobs for the authenticated customer, implying a read-only operation. However, it does not mention any potential side effects, rate limits, or response structure. The behavioral disclosure is adequate for a simple lookup.

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 extremely concise: two short sentences with no extraneous words. It front-loads the main purpose and adds a usage note, making it efficient for an agent to parse.

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 tool's simplicity (zero parameters, no output schema), the description covers the essential purpose and usage context. However, it does not describe the return format or specify ordering of results, which could be useful for an agent. Overall, it is mostly complete but missing minor details.

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?

There are no parameters, and schema description coverage is 100%. The description adds no parameter information, which is acceptable since none exist. The baseline of 4 applies as the schema already fully covers the parameter semantics.

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 ('Return') and the resource ('the authenticated customer's upcoming scheduled jobs'). It distinguishes from sibling tools like 'cancel_job' and 'reschedule_job' by specifying it is meant to be called before those actions to obtain the job ID.

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 explicitly instructs to 'Call this before rescheduling or cancelling to get the job ID,' providing clear when-to-use guidance. The sibling tools include reschedule_job and cancel_job, so the description effectively directs the agent to use this tool as a prerequisite.

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