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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, and the description adds genuinely new behavioral facts: the tool performs no UI action itself, the output is a sequence of screens/buttons/fields, and execution requires the browser toolset. The note about Yardi having no self-serve API for Breeze further sets expectations, though the phrasing is tangential to what the agent needs at call time.

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 ('opens nothing by itself') is front-loaded, which is good, but the sentence is a run-on that mixes purpose, return format, follow-up tooling, and an API-availability aside in one breath. The 'checked 27 Oct 2026' parenthetical adds noise without helping the agent invoke the 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?

With no input parameters and no output schema, the description carries the burden of explaining what comes back, and it does so ('step by step (screens, buttons, fields)'). The only remaining gap is how to hand off cleanly to the browser tools after reading the guide, which is implied rather than spelled out.

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 and the schema is fully closed, so there is nothing for the description to disambiguate. Baseline 4 applies.

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?

States a specific verb and resource ('Read tenant ledger') scoped to the user's own Yardi account, and clarifies the deliverable is step-by-step instructions rather than the data itself. It does not explicitly distinguish itself from the sibling read tool yardi_list_tenants_and_balances, so it falls short of a 5.

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?

Explicitly warns that the tool 'opens nothing by itself' and directs the agent to follow up with the cotlet_browser_* tools in the Yardi Cloud Browser, which is concrete workflow guidance. It stops short of stating when to prefer this over yardi_list_tenants_and_balances for balance data.

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