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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is scope ('public' mission visibility) and the disclosure that tx hashes come 'with explorer URLs when present' — conditional return content the agent would otherwise not anticipate. It stops short of saying what happens for a nonexistent/inaccessible id (error vs empty), which is the remaining behavioral gap.

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?

One sentence of purpose with return fields parenthesized, then a one-clause imperative for sequencing. Front-loaded with the verb and resource, zero filler, nothing repeated from annotations or schema.

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?

No output schema exists, so the field enumeration is load-bearing and it is provided; the sibling dependency is stated; the sole parameter's origin is given. For a one-parameter, idempotent read tool, an agent has everything needed to invoke it correctly.

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 0%, so the description must carry the parameter, and it does the most important part: the id is numeric and originates from list_missions, which is the only thing an agent needs to source it correctly. Minor mismatch — the schema accepts a string up to 64 chars via anyOf while the description says 'numeric id' — but the provenance hint outweighs that.

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?

Specific verb ('Fetch one public mission') plus resource and the exact projected fields (description, requirements, acceptance criteria, reward, deadline, moneyState, tx hashes). It distinguishes itself from list_missions by stating it returns a single mission and enumerating detail fields, so an agent can separate the two 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?

Explicitly routes provenance ('id from list_missions') and gives a hard sequencing rule: 'Read it before claim_mission or submit_work.' Both the alternative for enumeration and the downstream dependency are named, leaving no inference required.

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