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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description is consistent with them. Beyond that, it adds real behavioral context: the return value is procedural guidance (screens, buttons, fields), the tool performs no mutation by itself, and follow-up execution must happen through the cotlet_browser_* tools. The API-availability note explains why a browser-based path is required rather than a direct integration.

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 critical behavior (it returns steps, it does nothing itself, then use browser tools) is present but buried behind an opening clause that sounds like an action. The trailing API paragraph is dense, includes a dated audit claim, and is only loosely connected to invoking the tool, so several words do not directly earn their place in a routing decision.

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, no-output-schema guide tool, the definition covers what comes back, what it does not do, and which tools to use next. It is nearly complete; only the shape of the returned steps (single block vs. per-screen detail) is left unspecified, which is minor given annotations already establish it as a safe read.

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 input schema has zero parameters and 100% description coverage, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly does not invent parameter talk.

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 (contracts) and a specific account context (the user's own Studio Ninja account), and it clarifies that the tool returns step-by-step instructions rather than performing the send. The opening sentence, however, reads as an action ('Send contract... from ChatGPT, Claude or any AI agent'), so an agent skimming may briefly believe this is the write operation; the corrective 'opens nothing by itself' only lands in the second sentence.

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 an explicit sequence: call this first to get the screens/buttons/fields, then act with the cotlet_browser_* tools in the Studio Ninja Cloud Browser. That is genuine when-to-use guidance tied to named alternatives. It stops short of stating when NOT to use it (e.g., a sibling guide tool or the cotlet_app_guide general entry point), so it is clear but not fully branch-complete.

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