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

Annotations already flag destructiveHint=true and openWorldHint=true; the description goes beyond them by disclosing that a None value deletes an attribute, that validate_only performs a dry run returning the constructed body without writing, and that unknown IDs surface as http_error. It stops short of stating permission/scope requirements or rate limits, but the mutation risk and its mitigation are well covered.

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?

Front-loads the purpose, then proceeds mode-by-mode and parameter-by-parameter with no filler sentences. It is dense and telegraphic in places, and the parenthetical type glossary is compact rather than beautifully structured, but nothing is wasted.

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?

An output schema exists, so return values need not be described here. For a four-parameter tool with zero schema documentation and free-form attribute objects, the description covers modes, value encodings, deletion semantics, dry-run behavior, workspace scoping, and error behavior; only discovery of valid attribute IDs remains an explicit dead end.

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?

Schema coverage is 0%, so the description carries the full burden and does so: it defines the action values, the {attribut_id: wert} mapping shape, and the value encoding for each type (String/Liste=URL, Bool, {'enum': ...}, {'set': [...], 'unset': [...]}, None=delete). validate_only and workspace (optional when a single workspace exists) are also explained.

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 concrete verb+resource pair ('GBP-Attribute lesen/setzen') and scopes it with examples of attribute families (URLs such as LinkedIn/Termin, Amenities, Zahlung, Enum-/Mehrfachauswahl). An agent can distinguish this from gbp_update_profile or gbp_manage_hours by the 'attributes' framing, though no sibling is named explicitly to sharpen the boundary.

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?

Explains the two modes clearly (action: get | set) and gives real usage constraints: get returns only set attributes, available attribute IDs cannot be discovered through this tool, and unknown IDs yield http_error. It lacks explicit routing against sibling tools like gbp_update_profile or gbp_location_info, so it earns a 4 rather than a 5.

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