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

With readOnlyHint=true and openWorldHint=false already declared, the description adds real value by stating 'opens nothing by itself' and that the return is instructional content (screens, buttons, fields). That return-shape disclosure matters since there is no output schema. It does not say whether the steps vary by role or ResMan configuration.

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 instruction and follow-up path are front-loaded, which is good, but 'from ChatGPT, Claude or any AI agent' is marketing filler that earns no place. The trailing API/partner note with a verification date is useful context but adds bulk to an otherwise short definition.

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, read-only guidance tool with no output schema, the description covers what it returns, that it has no side effects, and what to do next. Sufficient for correct invocation; only the absence of any scope detail (e.g., which resident or account is implied) leaves a small 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 no parameter meaning to convey and the baseline applies. The description correctly implies no inputs are needed to obtain the guidance.

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 resource (resident ledger) and, critically, clarifies that the tool returns step-by-step instructions rather than the ledger data itself. This corrects the misleading 'Get ...' framing in the name/title. It doesn't explicitly distinguish itself from the resman_list_* siblings, which is the remaining gap.

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?

Gives a clear workflow: call this to get the steps, then execute them with the cotlet_browser_* tools in the ResMan Cloud Browser. The note that ResMan's official API is restricted to approved Integration Partners explains why the browser path is required. No explicit when-not-to-use condition is stated.

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