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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description adds the key behavioral fact that it 'opens nothing by itself' and returns instructional text rather than performing the action. It also explains why the tool exists (no official MCP server, API v2 only). Missing is any hint about the shape/size of the returned steps or failure modes.

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?

Purpose and behavior are front-loaded in the first two clauses, and the sequencing instruction follows immediately. The trailing sentence about Teamleader's public API and the 'checked 20 Oct 2026' date is marginally useful rationale but is the least load-bearing part of the text.

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 output schema, the description carries the burden of explaining the return value, and it does: step-by-step screens, buttons, and fields. It also tells the agent which tool family to use next, closing the loop. Only a note on what to do if the guided steps fail would make it fully complete.

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 and the baseline of 4 applies. Schema coverage is 100% with additionalProperties false, so the empty-input contract is unambiguous.

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 the resource (invoice reminder) and clarifies what actually happens: it 'Returns how to do it in Teamleader step by step (screens, buttons, fields)'. This corrects the potentially misleading 'Send' verb in the name, so an agent understands this is a guidance tool rather than an executing one. It does not explicitly contrast itself with the sibling cotlet_app_guide, which keeps it from a 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 operational sequence: call this first, then 'do it with the cotlet_browser_* tools in the user's Teamleader Cloud Browser'. The context for use is explicit. It stops short of stating when NOT to use it (e.g. versus cotlet_app_guide, or when the user wants a read-only listing via teamleader_list_overdue_invoices).

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