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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds meaningful return-content context (it reports token validity, roles, and next steps, plus guide_repo / guide_entry / guide_version), which is valuable because no output schema exists; the only redundancy is restating 'Rein lesend'.

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 content is front-loaded under 'WICHTIG', which is good, but the text is a dense bilingual paragraph and the trailing '| EN: auth, status, codeberg, guide, skill' keyword list is search-engine padding that does not help an agent decide or invoke. 'Rein lesend' also repeats the readOnlyHint annotation.

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 return-value burden and does so adequately: it names the auth facts reported (validity, roles, next action) and the guide_* fields returned. It stops short of describing the full response shape, but nothing an agent needs to call it correctly is missing.

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 is 4. It correctly signals a no-argument diagnostic call rather than implying any filtering or input is needed.

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 states a specific verb+resource: it diagnoses the auth state of the current connection, naming exactly what is reported (bearer-token validity, roles) and what to do next. This clearly separates it from siblings like login, refresh_access_token, or change_password, which mutate credentials rather than report status.

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 an explicit triggering condition — call it when unexpectedly few tools are visible — and explicitly rejects the wrong behavior ('statt zu raten' / instead of guessing). It also points to the platform guide for the broader workflow, so the agent knows both when to call it and where to go afterwards.

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