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

Annotations only declare it is a non-destructive write; the description adds real behavioral context beyond that: the offer is delivered to the client by email, with fallback delivery via the operator, and links are forbidden in the content. It still omits what happens on failure or whether an offer can be withdrawn, but the delivery path and content constraint are valuable disclosures.

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 short, front-loaded sentences with no filler; the core action leads and constraints follow. Slightly dense but every clause carries information.

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?

Covers the consent gate, delivery mechanism and content restriction, which is solid for a mutation tool. With no output schema, however, it says nothing about the result of submission (success confirmation, rejection, duplicate offers) and leaves job_id semantics unaddressed.

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 71% and already documents name, contact, message, text_only and consent, including the consent/privacy condition. The description reinforces that contact and price go to the client but adds little beyond the schema, and says nothing about job_id or the price_eur bounds.

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+resource: submitting an offer (Angebot) to a job posting (Gesuch), and enumerates the payload (name, contact, price, message). It is distinguishable from create_job and submit_review by resource, though it never explicitly contrasts itself with the sibling contact_provider, which is the closest alternative action.

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 one hard prerequisite — the offer may only be sent after the user's consent — which is genuinely actionable. However, it offers no guidance on when to prefer this over contact_provider or how it relates to the job lifecycle (e.g. must the job still be open), leaving selection between siblings to inference.

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