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

Annotations already declare readOnly/destructive/idempotent, so the bar is lower, and the description still earns credit by stating 'opens nothing by itself' and disclosing the return shape (step-by-step screens, buttons, fields). The API/MCP-beta aside adds provenance but not behavior. It does not say what happens if the user lacks permission to request time off or how long the instructions remain valid.

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 first two sentences are front-loaded and load-bearing: what it returns, what it does not do, and how to act on the output. The closing sentence about Personio's public REST API and closed-beta MCP server (with a future check date) does not help an agent decide or invoke this tool and reads as promotional filler.

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 parameters, no output schema, and strong annotations, the description covers what an agent needs: it is a read-only guidance tool whose output feeds the cotlet_browser_* tools. The only real gap is the absence of any precondition about having a Personio browser session open before attempting the follow-up steps.

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?

Zero parameters and no schema properties, so there is nothing to disambiguate; the baseline for a parameterless tool applies. The description correctly implies no user/date inputs are needed here because the real inputs are gathered by the browser tools downstream.

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 specific resource (time off in Personio) and explicitly corrects the impression created by the name 'request': it 'returns how to do it in Personio step by step (screens, buttons, fields)' rather than submitting anything. That distinguishes it from a mutating action, though it never names a sibling tool, so differentiation is descriptive rather than comparative.

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 to get instructions, then execute them 'with the cotlet_browser_* tools in the user's Personio Cloud Browser.' What is missing is any exclusion or routing rule — nothing says when to prefer this over personio_list_absences, personio_log_attendance, or personio_approve_time_off, nor any prerequisite such as needing an existing browser session.

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