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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses that the tool 'opens nothing by itself' and returns the steps, screens, buttons and fields needed. It also notes Avantio has official APIs but no official MCP server, which explains why a browser workflow is required. It stops short of stating account/session prerequisites for the Cloud Browser.

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 useful content (returns instructions, does not act, then use browser tools) is front-loaded, but 'from ChatGPT, Claude or any AI agent' is filler and the API/MCP aside is a long clause that is only marginally relevant to calling the tool.

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?

With no parameters and no output schema, the description does the important work by describing what is returned (step-by-step screens, buttons, fields) and what the agent should do next. It could be slightly more complete about required session state and failure modes.

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; baseline 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 verb and resource (read calendar) and then clarifies the actual mechanism: it returns step-by-step in-app instructions rather than data. The leading sentence reads as if it performs the read, which slightly muddies the purpose, but the following clause corrects that ambiguity.

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 explicitly routes the agent to the follow-up path: get the instructions here, then execute with the cotlet_browser_* tools against the user's Avantio Cloud Browser session. It doesn't state when NOT to use it (e.g., instead of a direct API sibling), but the intended workflow is unambiguous.

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