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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, but the description adds genuinely non-derived context: the tool returns procedural steps rather than data and 'opens nothing by itself'. It also explains the surrounding situation (Avantio has official APIs but no official MCP server), which justifies why browser automation follows. Minor weakness: it does not describe the shape or length of the returned steps.

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 two clauses are front-loaded and useful, but the trailing sentence listing Avantio's PMS/Web/Accounting APIs and an unverifiable 'checked 31 Oct 2026' date is padding that does not help an agent decide or act. The opening sentence also spends words on 'from ChatGPT, Claude or any AI agent', which adds no selection value.

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 guidance tool with full annotation coverage and no output schema, the description covers what it returns (step-by-step screens, buttons, fields), what it does not do (opens nothing), and what to do next (cotlet_browser_* tools). What is missing is any statement of the returned content's boundaries, such as which booking views or filters the steps cover.

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 schema declares zero parameters with additionalProperties false, so there is nothing for the description to disambiguate. The baseline for a parameterless tool applies, and the description does not introduce any phantom inputs the agent might try to supply.

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 eventually clarifies that the tool 'Returns how to do it in Avantio step by step (screens, buttons, fields) and opens nothing by itself', which is a specific and useful statement of purpose. However, it opens with 'List bookings in the user's own Avantio account', which reads as if the tool returns booking data rather than instructions, creating ambiguity about whether an agent gets data or a procedure. An agent can figure it out, but only after reading the whole paragraph.

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 follow-through guidance: 'then do it with the cotlet_browser_* tools in the user's Avantio Cloud Browser', which tells the agent what to do after calling. It offers no guidance on when to prefer this over data-returning siblings such as avantio_get_booking or avantio_list_tasks, so the selection logic among the Avantio tools is left implicit.

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