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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is covered. The description usefully adds what is returned ('how to do it step by step – screens, buttons, fields') and that it 'opens nothing by itself', which is valuable since there is no output schema. However, 'Clio's official API: Yes.' is cryptic and unexplained, and nothing is said about whether the returned steps are tied to a specific Clio UI version or what happens if the browser session is not authenticated.

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 content is front-loaded and short, but it is delivered as one dense semicolon-chained sentence plus a dangling fragment ('Clio's official API: Yes.') that adds no actionable meaning. The lead clause duplicates the tool name and title instead of immediately stating the instruction-return behavior.

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 rich annotations and no output schema, the description covers purpose, return content, and the follow-up tool family. Missing only minor context: authentication/session preconditions and any statement about instruction staleness.

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; the schema is closed (additionalProperties: false) and complete. Baseline of 4 applies for a no-parameter tool.

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 states that the tool returns step-by-step instructions (screens, buttons, fields) rather than performing the search itself, and the lead verb/resource matches the name 'search matters'. The opening sentence 'Search matters in the user's own Clio account from ChatGPT, Claude or any AI agent' reads like execution and is only corrected by the later clause, creating some split messaging. Still, an agent can tell this apart from the cotlet_browser_* executors.

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 gives a clear handoff sequence: call this to get the steps, then act with the cotlet_browser_* tools in the Clio Cloud Browser. It does not state when not to use it (e.g., vs. cotlet_app_guide or vs. direct Clio-native tools), and it doesn't mention prerequisites such as an already-open authenticated Clio session.

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