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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond that: the required scope `cv:lesen`, and the constraint that the agent cannot accept an offer on the user's behalf but must hand over the `zustimmungsseite` link. It does not cover pagination or volume limits, keeping it just short of a 5.

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-loaded with the trigger condition, then return contents, then the acceptance constraint and link, then scope. Sentences are dense and purposeful, though the return-value enumeration partially duplicates what the output schema already declares.

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 the description needn't detail return shape, and it still names the key fields; auth scope and the accept-on-website constraint round it out. The only omission an agent might want is that `nurOffene` can be set to false to include answered offers.

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?

The single parameter `nurOffene` has full schema description coverage, so the schema already explains that false also returns answered offers. The description never mentions this filter, so it adds nothing on top of the structured field. Baseline 3 applies.

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 (list employer introduction offers / Vermittlung) and enumerates the returned fields: employer, job, and when the user was asked. An agent can distinguish it from decline_employer_introduction and withdraw_employer_introduction without opening any schema.

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 an explicit trigger ("Use this when the user asks whether Jobroulette wants to introduce them to an employer") and an explicit exclusion: acceptance is not done here, only by the user on the Jobroulette website via the `zustimmungsseite` link. That routes the agent away from the sibling mutation tools by name of action.

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