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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds genuinely new behavior: it performs no navigation itself, returns a screen/button/field walkthrough, and requires chaining into cotlet_browser_* tools. The note that Yardi offers no self-serve API for Breeze explains why the browser path exists, though return format details remain thin.

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 message — instructions only, then execute via browser tools — is front-loaded and useful. However, "from ChatGPT, Claude or any AI agent" is marketing filler that adds no selection value, and the dated API footnote is tangential padding in a three-sentence description.

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 full annotation coverage, the description carries the remaining burden of explaining what comes back and what to do next, and it does both. A brief note on the shape of the returned steps (e.g., ordered list vs. prose) would close the last gap.

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 and the baseline of 4 applies. The description correctly implies no inputs are needed by describing a parameterless instructional lookup.

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 states a specific verb and resource ("List tenants and balances in the user's own Yardi account") and then clarifies the actual deliverable: step-by-step instructions for performing the task, not the data itself. That reframing is important and distinguishes it from siblings like yardi_read_tenant_ledger, though the ledger sibling is never named explicitly.

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 explicit sequencing guidance: this tool produces the plan, then the agent executes with the cotlet_browser_* tools in the Yardi Cloud Browser. The "opens nothing by itself" clause makes the boundary between this tool and the browser tools clear. It lacks an explicit when-not-to-use or a pointer to a direct-data alternative such as yardi_read_tenant_ledger.

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