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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely non-redundant behavior: it opens nothing by itself, returns screen/button/field-level instructions, and notes that the official Open API is limited and plan-dependent. That is real value beyond the annotations, though the API remark is contextually loose.

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 is front-loaded and clear, but the opening phrase ('from ChatGPT, Claude or any AI agent') is promotional filler and the closing API/date footnote is tangential to calling the tool. Both could be trimmed without losing 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 input schema, no output schema, and rich annotations, the description carries the burden of explaining what comes back and what to do next, and it does both. A slightly crisper statement of the return shape and the handoff condition to cotlet_browser_* would make it complete.

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 per the baseline there is nothing for the description to disambiguate. It does not waste space inventing parameter guidance, which is appropriate.

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 a specific resource (skip-trace results in REsimpli) and, importantly, clarifies that the tool does not fetch data itself but returns step-by-step instructions (screens, buttons, fields). It also names the sibling family (cotlet_browser_*) that actually performs the actions. The only weakness is that the title/name 'get skip-trace results' oversells what the tool returns, though the body corrects this.

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 follow-on path: use this for the how-to, then execute with cotlet_browser_* tools in the REsimpli Cloud Browser. However, it never states when NOT to use it (e.g., versus the API-backed resimpli_* siblings like resimpli_create_lead) or what preconditions exist, so selection against alternatives is only implied.

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