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

Beyond the annotations, the description adds the key behavioral fact that this tool only returns instructions and 'opens nothing by itself,' which prevents an agent from expecting an invoice list back. The note that Teamleader has a v2 API but no official MCP server explains why a browser-driven guide exists, though it doesn't describe the shape or length of the returned guide.

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 point comes first and the browser-handoff sentence is actionable, but the trailing API/MCP-server remark reads as vendor justification rather than information needed to invoke the tool. The 'ChatGPT, Claude or any AI agent' and 'checked 20 Oct 2026' details add length without helping selection.

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-destructive guide tool with no output schema, the description covers the essentials: what it returns at a high level, that it performs no action, and where the real action happens. The main omission is how the returned steps are structured and whether they are tied to a specific Cloud Browser session.

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 no parameter semantics to explain; the description correctly implies no inputs are needed. Nothing is added or contradicted relative to the empty schema.

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 first sentence says 'List overdue invoices,' but the second sentence reveals the tool actually returns step-by-step instructions and 'opens nothing by itself' — the real behavior is guidance retrieval, not data listing. The description does disclose this, but the name/title and the opening verb still point away from what the tool does, and it never distinguishes itself from the sibling cotlet_app_guide, which sounds like the same kind of guide tool.

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 one useful workflow cue: use this for the how-to, then perform the action with cotlet_browser_* tools. It does not say when to pick this over cotlet_app_guide or the sibling teamleader_* tools, nor does it state prerequisites such as needing an open Cloud Browser session.

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