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

Annotations already declare readOnly/idempotent/non-destructive, and the description reinforces this with 'opens nothing by itself', which resolves the apparent tension between 'Add' and readOnlyHint. It also discloses the return shape (step-by-step screens, buttons, fields) and the required companion tool family. Missing are auth/prerequisite context and any note on staleness of the returned UI 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 core behavior and the handoff are front-loaded in two dense sentences. Minor padding exists in 'from ChatGPT, Claude or any AI agent' and the cryptic trailing 'Clio's official API: Yes.', which costs clarity without adding actionable meaning.

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?

With no output schema and no parameters, the description carries the burden of describing the return value, and it does so concretely. It is nearly complete for a guidance tool, with only prerequisite/auth expectations and the relationship to other Clio guide tools left implicit.

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 nothing for the description to disambiguate and the baseline of 4 applies. The absence of parameters is consistent with a guidance-only tool, though the description doesn't explain how matter context is conveyed (it implicitly comes from the browser session).

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?

Names the specific verb and resource ('Add matter note') and immediately scopes what the tool actually produces: step-by-step instructions rather than the mutation itself. It distinguishes itself from the cotlet_browser_* siblings by naming them as the follow-up execution tools, so an agent can tell what this tool does versus what it does not.

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 two-step workflow: call this to get screens/buttons/fields, then perform the action with cotlet_browser_* in the user's Clio Cloud Browser. It lacks an explicit 'do not use this if...' exclusion and doesn't mention alternatives like cotlet_app_guide, so it stops short of a full routing rule.

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