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

With only readOnlyHint=false from annotations, the description carries real weight and delivers: a passing submission is counted as foreign work in project100_kpi and pays one entitlement of 0.1 RACOIN vesting in 20 days, while a failing one counts as nothing. It discloses outcome semantics and consequences far beyond the annotation, though it omits permission or rate-limit details.

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 front-loaded sentences with no filler; the pass/fail outcome is stated efficiently. The closing clause ('deliberately, so the number stays honest') is editorial but conveys intent in a few words.

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 consequential mutation tool with no output schema, the description covers the key behavioral outcomes (kpi credit, entitlement payout, vesting, failure handling) that an agent needs before invoking. It leaves the response shape unexplained, but that is a minor gap against otherwise rich behavioral coverage.

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 100%, so both params (task_id, payload) are already well documented in the schema, including the nested 'abgabe.felder' reference. The description adds framing ('that task's own criterion') but no parameter-level syntax beyond the schema. Baseline 3 is appropriate.

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: submitting a payload against one of the open tasks, with the payload checked against that task's own criterion. It is distinguishable from the project100_tasks listing sibling, though it doesn't name siblings explicitly. Clear purpose without full sibling differentiation.

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?

Implies usage ('one of the open tasks') and points at project100_tasks via the schema for the task id, but offers no explicit when-not conditions or named alternatives. The guidance is inferable rather than stated.

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