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

Goes well beyond the annotations: it discloses that the decision is irreversible ('a declined offer cannot be accepted later'), that repeat calls are no-ops ('a second call changes nothing and says so'), that the action is taken on the user's behalf, and the required scope 'vermittlung:zustimmen'. The irreversibility warning is material context that destructiveHint alone does not convey.

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?

Roughly four sentences with the trigger first, then the irreversibility warning, then the alternative route and scope. Nothing is padded; each sentence carries either a decision rule or a behavioral constraint.

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 single-param irreversible mutation this covers everything an agent needs: when to call, the ID source, the permanence of the effect, idempotent behavior, and the authorization scope. An output schema exists, so return values need no explanation here.

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 description coverage is 100% and the single 'id' param is documented as coming from list_employer_introductions. The description reinforces that provenance in passing but adds no format or validation detail beyond the schema, so the 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 (decline) and resource (an introduction to an employer), reinforced by the German legal term 'Vermittlungsvorschlag ablehnen' and the auth scope 'vermittlung:zustimmen'. An agent can separate this from list_employer_introductions and withdraw_employer_introduction without opening a 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?

Explicit trigger: 'Use this when the user does not want to be introduced to an employer for a job.' It also names the opposite path and explains that accepting is not done via a tool but by the user ticking a box on the page named in list_employer_introductions, so the agent knows when NOT to call this.

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