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

The annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, and the description is consistent with them: 'opens nothing by itself' confirms no side effects. Beyond the annotations it discloses the return content (screens, buttons, fields) and the required follow-up path via the browser tools, which is genuinely useful behavioral context.

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 about Teamleader's public API v2 and the absence of an official MCP server is justification/marketing rather than invocation guidance, and the 'checked 20 Oct 2026' date reads oddly. Trimming that sentence would make the definition tighter without losing anything an agent needs.

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, no-output-schema guidance tool, the description covers what comes back (step-by-step screens, buttons, fields) and what to do next (the cotlet_browser_* tools). The main residual gap is that it does not describe output structure or whether the note content must be supplied by the agent to the browser tools, but that is minor at this complexity level.

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?

There are zero parameters, so there is nothing schema-level to elaborate and no gap for the description to compensate for. The description does not introduce any parameter-related confusion, but also adds no input meaning because none exists.

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 (add a note in the user's Teamleader account) and, crucially, clarifies that the tool returns step-by-step instructions rather than performing the action. That clarification is needed because the name alone would suggest a write operation. It stops short of a crisp one-line statement of what the tool IS (a how-to/guidance tool), so 4 rather than 5.

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 first to get the screens/buttons/fields, then execute with the cotlet_browser_* tools in the user's Teamleader Cloud Browser. That is explicit guidance about sequencing and the alternative execution path. It does not state when NOT to use it (e.g., when the user already knows the steps or wants a different Teamleader action).

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