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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the scope of returned data, but does not disclose any behavioral traits such as aggregation behavior, latency, or auth requirements. It adds some value beyond annotations without contradicting them.

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 description is a single front-loaded sentence that conveys the tool's scope and contents efficiently. The bilingual repetition adds length but serves multilingual users; it remains appropriately sized and well structured.

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 burden of explaining return values, and it lists the major categories (address, signature, letterhead, presets, wallet, pricing). It does not detail the reasoning parameter, but since the tool is callable with zero parameters and returns a summary, the coverage is sufficient for an agent to use it correctly.

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?

There is one optional parameter, 'reasoning', with zero schema description coverage (0%). The description does not explain the parameter's purpose or format. Since the schema gives no help and the description does not compensate, parameter semantics are weakly documented.

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 opens with a specific verb and resource ('Liefert das Partnerprofil im Überblick') and enumerates the exact contents (sender address, signature, letterhead, presets, wallet summary, pricing model). This clearly distinguishes it from sibling tools like sender_profile_get or wallet_balance, which return narrower data.

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 description implies the tool is for getting a consolidated profile overview, but it does not explicitly state when to prefer it over individual sibling tools or when not to use it. It provides context (overview vs detail) without naming alternatives or exclusions.

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