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

The annotations declare readOnlyHint=true and destructiveHint=false, and the description reinforces this in plain language: it "opens nothing by itself" and only returns a step-by-step guide. It also explains the underlying constraint (Skedda's official API is read-only in beta with no MCP server), which justifies why browser automation is needed and is genuinely additive context an agent cannot infer from the annotations.

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?

Three sentences, front-loaded with the return value and the no-side-effect guarantee, then the follow-up tool path. Minor waste in the audience framing ("from ChatGPT, Claude or any AI agent") and a dated API note that sits oddly at the end.

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 tool with no output schema, the description covers what comes back (screens, buttons, fields), what it does not do (no booking executed), and the next step. Nothing essential for correct invocation is missing.

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 and the schema coverage is 100%, so there is no parameter meaning for the description to supply. Baseline for a parameterless tool applies.

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 action and resource but in a two-step framing: it first says "Create booking in the user's own Skedda account" and then immediately clarifies it "Returns how to do it in Skedda step by step (screens, buttons, fields) and opens nothing by itself." An agent can ultimately tell this is an instruction-returning tool rather than a booking mutation, but the initial sentence pulls in the opposite direction from the actual behavior.

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 workflow: call this to get the steps, then "do it with the cotlet_browser_* tools in the user's Skedda Cloud Browser." That names the alternative path explicitly. It does not address other Skedda siblings such as skedda_list_bookings or skedda_cancel_booking, so the routing guidance is partial rather than exhaustive.

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