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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds real value beyond them by promising a specific return shape (screens, buttons, fields shown step by step) and by stressing that it 'opens nothing by itself' — the crucial handoff detail for an agent. It stops short of describing error cases or what happens if the Workiz session isn't active.

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 core instruction is front-loaded in the first sentence, and the follow-up action is stated immediately after. The closing note on Workiz's official API is slightly digressive but earns its place by explaining why a browser-based path is necessary. No sentence is pure filler.

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 zero-parameter guidance tool with no output schema, the description covers what it produces (step-by-step Workiz instructions) and what to do next (cotlet_browser_*). An agent has enough to call it and act on the result. A brief note on return format or failure modes would close the remaining gap.

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 tool takes zero parameters, so there is nothing for the description to disambiguate. The baseline for a parameterless tool applies, and nothing in the description misleads about inputs.

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 uses a specific verb and resource ('Schedule job in the user's own Workiz account') and immediately clarifies the tool's real function: it returns step-by-step instructions rather than performing the action. It distinguishes itself sharply from the cotlet_browser_* executors, though it does not clarify its relationship to the sibling workiz_create_invoice or workiz_list_jobs tools.

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 states the workflow explicitly: call this first, then follow up with cotlet_browser_* tools in the Workiz Cloud Browser, and notes that nothing is opened automatically. It also explains why the official API route is unavailable (Ultimate plan only), which justifies using this path. What's missing is any guidance on when a job should not be scheduled this way or how it relates to the other workiz_* tools.

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