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, so the safety profile is covered. The description adds genuinely useful behavior beyond that: 'opens nothing by itself', meaning no browser session or navigation is triggered. The API-access caveat further explains why the browser path is the only option, though it does not describe the shape or length of the returned instructions.

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 workflow is front-loaded and readable, but 'from ChatGPT, Claude or any AI agent' is filler that adds nothing for an agent, and the closing API paragraph is long relative to its marginal value. The dated parenthetical '(checked 28 Oct 2026)' is odd and slightly distracting. It is serviceable rather than tight.

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 saying what comes back, and it does: step-by-step screens, buttons and fields. It also names the required follow-on tool family. A short note on whether the guidance is account-specific or generic would make it fully complete.

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 for the description to supply; the baseline of 4 applies. The description correctly implies no inputs are needed to obtain the guidance.

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 makes clear the tool does not return job board data but instead returns step-by-step guidance (screens, buttons, fields) for listing the job board in the user's own Tekmetric account. It distinguishes itself from the cotlet_browser_* siblings by naming them as the follow-on action. The only friction is the name 'list_job_board', which reads like a data-retrieval tool while the behavior is instructional, though the description does resolve that ambiguity.

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 states the workflow explicitly: call this to get the Tekmetric steps, then execute them with cotlet_browser_* in the user's Tekmetric Cloud Browser. It also pre-empts a plausible wrong path by noting the official partner API exists but is gated by application. It stops short of saying when to prefer this over a sibling like cotlet_app_guide, so it is strong but not exhaustive.

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