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

The description is consistent with the annotations and adds real value beyond them: it says the tool 'opens nothing by itself,' that it returns a step-by-step guide with screens, buttons and fields, and that the run happens against the user's own Rent Manager account via the Cloud Browser. It does not cover preconditions such as whether the user must already be signed in, which is the main remaining behavioral gap.

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?

Three sentences, front-loaded with the action and the key reframing that this is a guidance tool, then the execution path. The closing note about Rent Manager's API not being self-serve is tangential and the '(checked 11 Oct 2026)' date stamp adds noise, but the text stays short.

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, no output schema and a simple read-only contract, the description covers what an agent needs: what it returns, that it performs no writes, and which tools carry out the action. It stops short of saying what the returned instructions look like (format, length) or what to do if the Cloud Browser session is not authenticated.

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 4 applies. The description does not need to compensate for any schema gap.

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 names a specific verb+resource (post a charge in the user's Rent Manager account) and immediately resolves the ambiguity in the tool name by stating it returns step-by-step instructions rather than performing the action. It also distinguishes itself from the cotlet_browser_* siblings that actually execute the workflow. The only blemish is that the opening phrase 'Post charge' could briefly mislead an agent before the clarification lands.

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 an explicit two-step workflow: call this first to get the screens/buttons/fields, then execute with cotlet_browser_* tools in the Cloud Browser. It does not state when not to use it (e.g., when a direct API-backed sibling could handle the task) or contrast it with rent_manager_create_work_order, so exclusions are absent.

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