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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint false), it discloses the return shape (screens, buttons, fields), that nothing is opened by the tool itself, and where the real interaction happens (user's Joblogic Cloud Browser). The note that Joblogic's REST API is a paid developer module explains why the browser route is required, which is genuinely useful context.

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 key scoping fact (returns steps, opens nothing) is front-loaded, but the definition carries filler such as "from ChatGPT, Claude or any AI agent" and a long closing sentence about the Marketplace API with a checked date. These earn little for an agent deciding whether to call it.

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, no-output-schema guide tool, the description covers what comes back and what to do next, which is the critical missing piece otherwise. It stops short of describing how the guide output is structured or how to recover if the browser session is not authenticated.

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 no parameter meaning to convey; baseline 4 applies. The description correctly implies no inputs are needed by framing the call as a request for instructions.

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 names a specific verb and resource (list unpaid invoices) but immediately corrects the misleading name by saying it "Returns how to do it in Joblogic step by step ... and opens nothing by itself." That makes the actual purpose (a procedural guide, not a data fetch) clear, though the opening sentence still reads like the tool performs the 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?

It gives a concrete workflow: call this to get the steps, then execute them with the cotlet_browser_* tools in the Joblogic Cloud Browser. It does not say when to prefer this over siblings such as joblogic_list_jobs, nor when not to use it, so usage is implied rather than decided.

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