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

With no output schema, the description carries useful weight by disclosing what is returned (step-by-step screens, buttons, fields) and that it 'opens nothing by itself', which reinforces the readOnlyHint annotation rather than merely restating it. The closing line 'AppFolio's official API: Partly.' is cryptic and adds ambiguity rather than clarity.

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 operational core (returns instructions, then use browser tools) is front-loaded, but 'from ChatGPT, Claude or any AI agent' is promotional filler and 'AppFolio's official API: Partly.' is an unexplained fragment that costs the reader without informing them.

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?

For a zero-parameter guide tool with no output schema, the description covers what it returns and what to do next, which is the essential information. The only real gap is the unclear partial-API-support remark, which an agent cannot act on.

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, which is the baseline-4 case; there is nothing for the description to disambiguate at the argument level. The description does not confuse the issue with phantom 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 makes the key distinction that this tool does not fetch ledger data itself but returns a step-by-step AppFolio procedure (screens, buttons, fields). That is specific and disambiguates it from data-returning siblings like appfolio_run_report, though the name 'get_tenant_ledger' still pulls in the opposite direction and the description has to work to correct it.

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 states the follow-up path clearly ('then do it with the cotlet_browser_* tools in the user's AppFolio Cloud Browser'), which is real usage guidance. It gives no when-not guidance or explicit alternative when a different tool (e.g. cotlet_app_guide or appfolio_run_report) would be the better call.

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