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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description reinforces rather than repeats that by stating it 'opens nothing by itself' and hands off to the browser tools. The note that Rent Manager's official API is not self-serve explains why the browser path exists, adding context beyond the annotations.

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 earn their place, but the closing sentence about Rent Manager's official API and the '(checked 11 Oct 2026)' date is rationale rather than invocation guidance and adds noise to an otherwise tight definition.

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 returns, and it does: step-by-step screens, buttons, and fields. It also states what happens next, leaving only the exact response format 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 no parameter meaning to add and the baseline is 4. Nothing in the description misleads 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 says it creates a work order in the user's Rent Manager account, then immediately clarifies the real behavior: it 'Returns how to do it in Rent Manager step by step (screens, buttons, fields)'. That is a specific verb-and-resource statement an agent can act on, though the opening 'Create work order' phrasing sits awkwardly against a tool that 'opens nothing by itself'.

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 first to get the steps, then perform them with the cotlet_browser_* tools in the Rent Manager Cloud Browser. It does not explicitly contrast itself with rent_manager_post_charge or rent_manager_list_tenants, but the sequencing constraint is stated plainly enough to guide selection.

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