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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself', explaining why a 'create' tool is read-only. It also discloses the return shape (step-by-step screens, buttons, fields) and the reason no direct API path exists (Ultimate-plan-only REST API limited to jobs, leads, team members, time off). It stops short of stating preconditions such as an active/logged-in Cloud Browser session.

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 with the core behavior and the handoff to browser tools; every sentence has a function. The closing sentence on Workiz's API plan tiers and coverage is slightly verbose background, though it does justify why this is a guide rather than an API call.

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?

No output schema exists, and the description adequately describes what is returned, but with zero parameters it never explains how the agent should supply the invoice specifics (customer, job, line items) — presumably gathered elsewhere or during the browser steps. Mentioning that gap or the required Cloud Browser session state would make it complete for a workflow 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?

There are zero parameters, so the schema carries no burden and the baseline is 4. The description adds nothing about inputs, but none exist to explain.

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 states a specific resource (Workiz invoice) and, crucially, clarifies that the tool does not create anything but returns step-by-step Workiz instructions. The opening verb 'Create' is slightly at odds with the actual guide-returning behavior, but the second clause resolves it and separates this tool from the cotlet_browser_* executors.

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 gives an explicit workflow: call this to get the screens/buttons/fields, then perform the action with cotlet_browser_* in the user's Workiz Cloud Browser. It does not explicitly compare against cotlet_app_guide or explain when to call workiz_* API siblings instead, but the sequencing guidance is clear enough to act on.

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