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

The annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it 'opens nothing by itself' and returns instructional content rather than data, plus the note that Jane's official API is restricted to approved Technology Partners, which explains why browser automation is required. It stops short of describing the shape or length of the returned instructions.

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 fact, that this returns instructions and performs no action, is front-loaded in the first two sentences. The phrase 'from ChatGPT, Claude or any AI agent' is filler that adds no operational meaning, and the API note, while useful context, reads as an aside bolted onto the end.

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, non-mutating helper with no output schema, the description covers what it returns, that it has no side effects, and what to do next. The only real gap is not clarifying its relationship to cotlet_app_guide, which an agent choosing between instructional tools would need.

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 an empty object with additionalProperties false, so there is nothing for the description to disambiguate. Baseline 4 applies. The description correctly implies no arguments 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?

The description names a specific verb and resource ('Read accounts receivable in the user's own Jane App account') and then immediately clarifies that the tool actually returns step-by-step instructions rather than the data itself. That clarification is essential because the name alone would mislead an agent into expecting records back. It could distinguish itself more sharply from cotlet_app_guide, which appears to serve a similar instructional role.

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 does state the follow-on path: use the cotlet_browser_* tools in the Jane App Cloud Browser to actually perform the steps. However, it never says when to prefer this over the similarly-named cotlet_app_guide, nor when this is unnecessary (e.g., if the agent already knows the Jane workflow). Usage is implied rather than specified against alternatives.

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