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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Kein Schreibpfad' is largely redundant. What the description does add beyond structured data is the list of returned fields, valuable since there is no output schema. Missing: auth prerequisites and what happens if the profile is incomplete.

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?

Two short sentences, read-only constraint front-loaded, with the returned fields immediately after. The bilingual duplication is slightly redundant but serves keyword discovery rather than bloating the semantics.

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 parameterless read tool with full annotation coverage, the description covers the only real gap by enumerating the returned fields in place of a missing output schema. Nothing an agent needs in order to call it correctly is absent.

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 to disambiguate and the baseline is 4. The description correctly implies a no-argument call that returns the caller's own profile.

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?

States a specific verb and scope ('Eigenes Profil rein lesend abrufen') plus the exact fields returned (Name, E-Mail, Organisation, Notizen, Skills), so the agent knows precisely what it gets. It signals read-only intent ('Kein Schreibpfad'), which implicitly separates it from change_profile/change_password, but never names those siblings explicitly.

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?

The phrases 'Eigenes Profil' and the alias line 'who am i, my account, profile' give clear situational triggers, and 'Kein Schreibpfad' tells the agent this is not the tool for edits. It stops short of naming change_profile as the alternative for mutations, leaving that inference to the agent.

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