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 with the valuable, non-redundant disclosure that the tool 'opens nothing by itself' — critical for an agent that might otherwise assume a payment was submitted. It also notes the official REST API exists but is not self-serve, explaining why the browser route is needed. It stops short of stating failure modes, e.g. what happens if no DoorLoop browser session exists.

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 key constraint (returns instructions, performs nothing) is front-loaded in the second sentence, and the browser tool hand-off follows logically. The audience enumeration 'from ChatGPT, Claude or any AI agent' is expendable, and the dated API remark is tangential but does justify the tool's existence.

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?

There is no output schema, and the description compensates by describing the return value's shape (steps with screens, buttons, fields). For a zero-parameter read-only guide tool this is close to complete; the missing piece is the prerequisite state of the user's DoorLoop Cloud Browser before calling it.

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 schema has zero parameters at 100% coverage, so the baseline is 4. However, a payment-recording guide that accepts no arguments (no payment amount, tenant, or property) is a notable limitation the description never acknowledges or explains.

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 second sentence states precisely what the tool returns: a step-by-step DoorLoop walkthrough (screens, buttons, fields) and explicitly that it 'opens nothing by itself'. This resolves the ambiguity created by the name/title 'Record payment', which naively reads as a write action. It is clearly distinct from the cotlet_browser_* tools it names, but never distinguishes itself from the real DoorLoop API siblings (doorloop_post_rent_charge), leaving a small gap.

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 clear two-step workflow: call this for guidance, then execute with cotlet_browser_* tools in the DoorLoop Cloud Browser. What is missing is any exclusion — nothing says when NOT to use this versus the actual DoorLoop write endpoints or doorloop_post_rent_charge, and no prerequisites (signed-in session, browser already opened) are stated.

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