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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, and the description goes well beyond them: it discloses that a real e-mail is sent, that name/email must genuinely belong to the brand, that only request_id is returned (no creator details, no private contact data), the 10-creators-per-30-days free allowance, the unlock_required overflow behavior, and applicable terms. This is unusually rich behavioral context.

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?

Content is dense and front-loaded, with the effect, requirements and flow stated early in each language block. However, the entire description is duplicated verbatim in German, roughly doubling length without adding information; a single-language-plus-note structure would be materially leaner.

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 5-parameter, no-output-schema, non-read-only tool with open-world behavior, the description covers the effect, prerequisites, return value, quota limits, failure mode and escalation path. An agent has everything needed to decide whether and how to call it.

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?

With 0% schema description coverage the description must carry parameter meaning, and it does: it identifies name, email and creator_public_ids as required and sourced from a prior search, marks message and search_query as optional free text, and explains the [Name] placeholder substitution. It does not restate the stricter format constraints (creator_public_ids pattern, email regex), so a minor gap remains.

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 resource ('Triggers a deliberate brand request') and immediately explains the concrete effect: UGC VZ forwards selected creators' contact details to the brand by e-mail. It also names the sibling it hands off to (get_outreach_status via request_id), so an agent can distinguish it from get_creator/search_creators even without opening schemas.

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?

Explicitely defines prerequisites ('Creators must have been found via search_creators or get_creator'), the typical call sequence (search_creators -> get_creator -> request_outreach -> get_outreach_status), and exclusions ('No bulk requests, no test calls', 'only for serious, genuine requests'). It also states the quota/unlock path, which is exactly the kind of when-to-use guidance agents need.

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