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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with them by stating it 'opens nothing by itself' and only returns instructions. This is valuable because the name 'accept_a_job' would otherwise imply a mutation; the description pre-empts that misreading. It stops short of covering prerequisites (session/auth state) or failure behavior.

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 behavior ('returns how to do it step by step ... opens nothing by itself; then do it with the cotlet_browser_* tools') is front-loaded and earns its place. The trailing note about Checkatrade's official API is relevant justification for browser automation but is slightly tangential and carries an oddly specific future date.

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 no parameters and no output schema, the description carries the burden of explaining return values, and it does so (screens, buttons, fields) plus the follow-up tool family. That is sufficient to call the tool correctly. Minor gaps remain around preconditions and error handling, but nothing essential is absent.

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 beyond the schema, which is the baseline-4 case. No parameter detail is needed or missing.

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 ('Accept a job in the user's own Checkatrade account') and scopes it to the user's own account, so the action is unambiguous. It does not explicitly contrast itself with adjacent siblings such as checkatrade_send_a_quote or checkatrade_reply_to_a_lead, but the action is distinct enough to be selected without opening a schema.

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 clear workflow guidance: this tool returns step-by-step instructions and 'opens nothing by itself', after which the agent should execute the steps with the cotlet_browser_* tools in the Cloud Browser. That is an explicit alternative and division of labor. What is missing is a negative case — e.g., when not to call it, or what to do if the user is not logged in.

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