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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false; the description adds the crucial non-obvious behavior that it 'opens nothing by itself' and returns procedural instructions instead. It also discloses the absence of a public ClockShark API, which explains why browser automation is needed. It stops short of describing output format or length, but that is a minor gap given the read-only profile.

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 fact ('returns how to do it step by step, opens nothing') is front-loaded in the first sentence, with the follow-up tooling in the second. The closing note on the missing public API earns its place as justification. Minor redundancy from multi-vendor phrasing ('ChatGPT, Claude or any AI agent') and an oddly dated verification stamp.

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 description covers what comes back (screens, buttons, fields), what does not happen (no action taken), and what to do next. Nothing essential is missing, though the relationship to cotlet_app_guide is left unexplained.

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 baseline for a parameterless schema applies. No parameter claims are made that could conflict with the empty schema.

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 makes clear the tool produces a step-by-step walkthrough (screens, buttons, fields) for creating a ClockShark job rather than performing the creation. This resolves the tension with the name 'create_job' explicitly. It does not name a competing sibling like cotlet_app_guide, so differentiation is only partial.

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 sequencing guidance ('then do it with the cotlet_browser_* tools in the user's ClockShark Cloud Browser'), which tells the agent what to do after calling. However, it offers no when-not conditions and never mentions cotlet_app_guide or other guide tools as alternatives, leaving the choice between guide tools implicit.

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