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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself', which prevents an agent mistaking it for an action tool. It adds useful context about the return shape (screens, buttons, fields) but says nothing about auth, rate limits, or failure modes.

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 key correction (returns instructions, opens nothing) is front-loaded in the first sentence, and the follow-up tool guidance follows immediately. The trailing sentence on Studio Ninja's lack of a public API is longer than needed and carries a dated verification stamp, but it does justify why browser automation is required.

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, non-mutating guidance tool with full annotation coverage and no output schema, the description supplies everything needed: what it returns, that it performs no action, and which tools execute the plan. Only the precision of the returned instruction format could be spelled out further.

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 of 4 applies. The description correctly implies the only variable is the user's own Studio Ninja account context.

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?

States a specific resource (a Studio Ninja job booking) and immediately clarifies the actual verb: it returns step-by-step instructions rather than performing the booking. It also names the follow-up tool family (cotlet_browser_*) so an agent can distinguish this from an execution tool.

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?

Explicitly tells the agent to call this first for the click-path, then carry it out with the cotlet_browser_* tools in the user's Studio Ninja Cloud Browser. There is no explicit 'when not to use' or mention of the sibling studio_ninja_add_lead flow, but the sequencing guidance is unambiguous.

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