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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real non-obvious context beyond that: the tool performs no browser action itself and only returns instructions, which prevents an agent from assuming a side effect occurs. The trailing note about sevdesk's REST API is informational but adds little behavioral value.

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 a guide, opens nothing, hand off to cotlet_browser_* tools) is present but buried after a promotional clause about ChatGPT/Claude/AI agents. The trailing "checked 14 Oct 2026" API note and the future-dated verification are noise that does not help an agent decide or act.

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?

There is no output schema, so the description must carry the return-value burden; it partially does by naming step-by-step screens/buttons/fields. It stops short of describing the response shape or format, and never addresses what happens if the user's sevdesk account is not connected, which matters for a zero-parameter hand-off tool.

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 and the description correctly implies no input is required. With no parameters there is no semantic gap to fill, so the baseline of 4 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 name and title claim it lists open invoices, but the body reveals the tool returns a step-by-step guide ("screens, buttons, fields") rather than invoice data. The real behavior is stated, but the framing creates a genuine ambiguity about whether the tool ever returns actual invoice records, which is the first thing an agent needs to know.

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 concrete follow-up path ("then do it with the cotlet_browser_* tools in the user's sevdesk Cloud Browser") and explicitly says it opens nothing itself. However, it never says when to choose this over siblings like sevdesk_create_invoice or cotlet_app_guide, nor what prerequisites (logged-in session, connected account) must hold before calling.

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