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

The description explicitly discloses the key side-effect fact — it "opens nothing by itself" — which reinforces the readOnlyHint=true annotation rather than contradicting the write-flavored name. It also explains the rationale for the workaround (no self-serve API for Breeze). It stops short of describing output structure or the limits of the returned steps.

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 with some waste: "from ChatGPT, Claude or any AI agent" is vendor framing, and the "checked 27 Oct 2026" stamp is peripheral. The most decision-critical fact, "opens nothing by itself," sits mid-second-sentence rather than being front-loaded against the misleading "Post charge" name.

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?

No output schema and no parameters, so the description carries the burden, and it does explain what comes back (step-by-step screens/buttons/fields) and the hand-off to browser tools. The gap is that with zero parameters it never explains where the charge specifics come from — conversation context — leaving an agent unsure how to scope the request.

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 the schema has nothing to document and the baseline of 4 applies. The description offers no elaboration on how the agent should supply tenant/amount context, but with no parameters there is no schema gap to compensate for.

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?

"Post charge in the user's own Yardi account" plus "Returns how to do it in Yardi step by step (screens, buttons, fields)" makes clear this is a guidance generator, not an executor. The parenthetical enumerating screens/buttons/fields sharpens the output shape. It does not, however, differentiate itself from other yardi_* siblings such as yardi_read_tenant_ledger or yardi_create_work_order.

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 routes the agent forward by naming the follow-up path: "then do it with the cotlet_browser_* tools in the user's Yardi Cloud Browser." That is useful sequencing guidance. But it never states when to prefer this over going straight to the browser tools, nor prerequisites such as whether a browser session must already be open or how the specific charge details are supplied.

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