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

Annotations only say readOnlyHint=false / destructiveHint=false; the description goes far beyond by enumerating the concrete consequences of setting zielgruppe (adult mode off, real people refused, generation halts if the content check is down, export must mark the film as AI). It also discloses the conflict failure mode, the clearing semantics (empty string / empty list), and the replacement (not merge) behavior of zielmaerkte.

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 read/set distinction and the primary 'when to use' rule are front-loaded, and almost every sentence carries operational weight. It is, however, a dense and lengthy block; a few clauses (e.g. the detailed enumeration of every block type) run longer than strictly necessary for invocation decisions.

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?

Despite having no output schema, the description fully specifies the return payload (zielgruppe, zielmaerkte, zielgruppe_regeln, zielmarkt_checkliste) and even instructs the agent to pass the checklist to a human and flags that it is not legal advice. Nothing needed to invoke or interpret the call 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it explains the downstream effects of each zielgruppe value, the per-country checklist nature of zielmaerkte, and that the list replaces rather than appends. The only reason it isn't a 5 is that value syntax (the ISO/EU/UK code format) is already fully carried by the schema.

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?

Opens with a precise verb pair and resource: 'Read or set a project's audience (zielgruppe) and target markets (zielmaerkte).' It immediately splits the two call modes ('With project_id only: read') so the agent knows the tool is dual-purpose, and the resource is distinct from anything in the sibling list.

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?

Gives explicit triggering conditions ('whenever the project is made for children, families or teenagers') and a required ordering ('do it BEFORE creating characters or generating'). It also names the blocker condition for failure ('fails with a readable conflict while a digital double sits in the cast — take it out first') and clarifies that zielmaerkte blocks nothing, so the agent can reason about which parameter to set.

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