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

Goes well beyond the annotations by disclosing the key side effect: the offer is emailed automatically to the client (and to all households in shared jobs), plus the consent gate and the 'no internet links' content rule. It stops short of saying whether offers can be withdrawn or edited afterwards, which matters for a mutation tool.

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?

Three compact sentences with the action front-loaded, followed by delivery behaviour and constraints. No filler, though the 'no internet links' rule sits a little detached at the end.

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 10 parameters, no output schema, but full annotations, the definition covers the essential behaviour: who receives the offer, consent requirement, shared-job specifics. Missing only post-submission behaviour (confirmation, editability), which is a minor gap.

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 already 90%, so the baseline is 3. The description adds a rule not stated in the schema alone: shared jobs require separate_contracts=true, and it enumerates the core payload (name, contact, price, message) in context.

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 ('Als Anbieter ein Angebot zu einem Gesuch abgeben') and implicitly distinguishes it from create_job/join_job by framing it as the provider-side response to an existing job. An agent knows exactly what action is performed.

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 concrete preconditions: only after explicit user consent, and separate_contracts=true for shared jobs across multiple households. It does not explicitly contrast with sibling tools, but the context is clear enough to select correctly.

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