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

The description reinforces readOnlyHint by stating it 'opens nothing by itself', which is exactly the behavioral detail an agent needs to avoid assuming a side effect occurred. It also discloses external context (Skedda has only a read-only beta API and no official MCP server), explaining why browser tools are required; it omits any note on idempotency or the shape of the returned steps beyond 'screens, buttons, fields'.

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 constraint (returns steps, opens nothing) is front-loaded, but the text is a run-on chain of semicolon-joined clauses and includes a dated API-check note that is unlikely to matter at call time. It could be tightened without losing any decision-relevant information.

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 no output schema, the description covers what it returns and what it does not do, which is sufficient to invoke it correctly. The absence of an output schema means a slightly richer description of the returned step format would have helped, but nothing essential 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, so the baseline is 4 and there is no parameter meaning for the description to add. The schema is trivially complete with additionalProperties false.

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 action and resource (block out a space in the user's own Skedda account) and immediately clarifies that the tool returns step-by-step instructions rather than performing the block-out. It implicitly separates itself from the cotlet_browser_* execution tools, though it never explicitly distinguishes itself from skedda_create_booking or skedda_cancel_booking.

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 clear routing guidance: call this to get the screens/buttons/fields, then perform the action with cotlet_browser_* tools in the Skedda Cloud Browser. It does not state when-not to use it or contrast it with the other skedda_* booking tools, so the exclusion side is left to inference.

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