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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, and the description reinforces rather than contradicts them by saying it opens nothing by itself. It adds genuinely non-obvious context by explaining why the browser route exists: Joblogic's REST API is a paid Marketplace module for developers, which justifies this tool's existence over an API call.

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 behavior statement is front-loaded and the tool is compact. Some filler remains, notably 'from ChatGPT, Claude or any AI agent' and the 'checked 9 Nov 2026' date stamp, which do not help an agent decide whether to call the tool.

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?

With zero parameters and no output schema, the description adequately covers both what the tool returns (step-by-step screens, buttons, fields) and what the agent should do next. It stops short of describing the response format (structured steps vs. prose), which would fully close the gap for a guidance-type 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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning for the description to carry. It correctly introduces no phantom arguments and the empty schema is consistent with the described behavior.

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 resource (jobs) and scope (the user's own Joblogic account), then clarifies the actual behavior: it returns step-by-step instructions (screens, buttons, fields) rather than the job data itself. That clarification is valuable, but the opening sentence restates the name 'List jobs', which momentarily suggests the tool returns a job list and only gets corrected in sentence two. No differentiation from joblogic_list_unpaid_invoices is given.

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: get the steps here, then execute them with the cotlet_browser_* tools in the Joblogic Cloud Browser, and states that this tool 'opens nothing by itself'. That is clear context and a named downstream alternative, but there are no explicit exclusions (e.g., when to skip this and navigate the browser directly).

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