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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description reinforces this with the important disclosure that the tool 'opens nothing by itself' and merely returns screens, buttons and fields to follow. That is genuine value beyond the structured fields, since an agent might otherwise assume the call performs the listing. Minor deductions for the odd future-dated API note ('checked 31 Oct 2026') and for not describing the shape of the returned instructions in more detail.

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 is front-loaded, but the opening clause 'from ChatGPT, Claude or any AI agent' is filler, and the closing API sentence is redundant in phrasing ('Checkatrade's official API: Checkatrade has an official API...') and carries a suspect date. Two of the three sentences could be tightened without losing information.

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 tool with a full annotation set, the description covers what is returned (step-by-step screens, buttons, fields), what is not done (no browser action), and what to do next. It is essentially complete for an agent to call it correctly, with only the exact return format left unspecified.

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; baseline is 4. The description correctly implies no inputs are required, consistent with the empty schema.

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?

States a specific verb and resource (list new leads in the user's Checkatrade account) and then corrects the naive reading by explaining it returns step-by-step instructions rather than performing the listing. That correction is essential because the name/title alone would mislead an agent into expecting lead data back. It does not explicitly differentiate from the sibling checkatrade_browse_opportunities_board, which keeps it off a 5.

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?

Gives clear sequencing: call this first to get the procedure, then execute it with the cotlet_browser_* tools in the user's Checkatrade Cloud Browser. That is actionable guidance about the workflow and names the concrete alternative tool family. It stops short of explicit when-not-to-use guidance or a direct comparison against the Checkatrade siblings such as browse_opportunities_board.

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