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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds genuinely non-obvious context beyond them: the tool opens nothing by itself, its output is a step-by-step UI procedure, and SimplePractice has no public API for practices. That last point explains why a browser-driven path is required, which is real value.

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 behavioral fact is buried in the second sentence after a leading sentence that overstates what the tool returns. "From ChatGPT, Claude or any AI agent" is filler, and the parenthetical API-check date is oddly precise noise. The content is useful but not front-loaded.

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 guidance tool with no output schema, the description does the essential work: it says what comes back (screens, buttons, fields), that nothing is executed, and which tool family performs the action. Only the exact shape/scope of the guide output remains unspecified, which is minor.

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 is zero-parameter, so the baseline is 4. The description correctly implies no inputs are needed and adds nothing misleading about arguments.

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 resource (outstanding balances in SimplePractice) but the verb 'List' suggests data retrieval while the body says the tool actually "Returns how to do it in SimplePractice step by step (screens, buttons, fields)." An agent must read to the second sentence to learn the call produces a procedure, not balances. The mismatch between the name and the real output keeps this below clear.

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 route the follow-up action: "then do it with the cotlet_browser_* tools in the user's SimplePractice Cloud Browser," which tells the agent what to do next. However, it gives no guidance versus alternatives such as cotlet_app_guide or the other simplepractice_list_* tools, and no statement of when this tool is inappropriate.

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