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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds meaningful context beyond them by labeling the output a 'public-safe canonical record', signaling the data is sanitized rather than internal detail.

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?

A single tight sentence with no wasted words, and the retrieval purpose is front-loaded. It is efficient, though it packs the usage rationale into the same clause rather than separating concerns.

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 an output schema present, return values need not be explained, and the single fully-documented parameter needs no extra description. The description supplies sufficient context for a read-only single-record lookup, though it could name the sibling it precedes.

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%; the id parameter has a pattern, length bounds, and example already documented in the schema. The description adds no additional syntax or format guidance, so the baseline of 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 (Read) and resource (public-safe canonical record for one paid WORKNET opportunity), which is clear. It implies single-item retrieval versus the plural sibling bursia_worknet_paid_tasks, but never names that sibling, so differentiation is only implicit.

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?

The phrase 'before deciding whether to prepare internal work' gives implied usage context, tying it loosely to the prepare_mission workflow. However, no alternatives are named and no explicit when-not guidance is provided, leaving the agent to infer when this beats the paid_tasks list.

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