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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this rather than contradicting it by stating 'opens nothing by itself'. It adds genuinely useful behavior detail: the return is step-by-step screens/buttons/fields, and it discloses that official API access requires the AppConnections add-on and an admin-created key. Return format and pagination are not applicable here.

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 first two sentences are front-loaded and efficient, but the third sentence drifts into API v2 endpoint enumeration (jobs, contacts, estimates, photos, job messages, payments) and an administrator key detail that is tangential to invoking this tool. That detail could be trimmed or moved to a separate reference without losing anything an agent needs to call this 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?

For a parameterless, non-mutating guidance tool, the description covers what it returns, that it performs no action, and how to proceed afterward. The API add-on note is extra context rather than a gap. It is complete enough for an agent to select and use it correctly.

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?

There are zero parameters, so there is no schema semantics to compensate for. The baseline for a parameterless tool is 4, and the description does not mislead about inputs.

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 uses a clear verb+resource ('Add job note') and, crucially, immediately clarifies that the tool only returns step-by-step instructions rather than performing the write. That clarification is what separates it from a true mutation tool. It stops short of naming a specific sibling (e.g., cotlet_app_guide) as an alternative, which keeps it out of 5 territory.

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 context clearly: get the steps here, then execute them with cotlet_browser_* tools in the AccuLynx Cloud Browser. That is an explicit workflow handoff, not just implied usage. It does not state when NOT to use this tool or name a competing guidance tool, so it lands at 4 rather than 5.

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