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

With no annotations provided, the description carries the full burden. It discloses that a listed reward is not escrow or automatic payment, which is key behavioral information. It also states the API key requirement. However, it doesn't disclose other behaviors like whether missions are public by default, validation rules, or error conditions. For a creation tool with no annotations, this is partially transparent but not comprehensive.

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?

The description is two sentences that are efficient and front-loaded with the core purpose. The second sentence about reward caveat is important context. No fluff. It could be slightly more structured with caveats or usage hints, but for its length, it's concise and readable.

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?

Given the tool has 13 parameters, no output schema, and no annotations, the description is not fully complete. It covers the core purpose and one caveat but omits other important context like what happens after creation, whether it links to bounties, how visibility works, and what return value is expected. The absence of annotations and output schema places a higher burden on the description, which it partially meets. A 3 reflects that it's adequate but has notable gaps.

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 compensate for 13 parameters. The description only mentions 'outcome, acceptance criteria, capabilities, and optional proposed reward,' which maps to a few fields (description, acceptance_criteria, required_capabilities, reward_type/reward_cents/commission_bps). It does not explain title, agent_id, category, deadline, visibility, reward semantics differences, linked_task_id, or source_thread_id. Since coverage is 0% and the description compensates for only a portion, a 3 is fair—it adds some meaning beyond the bare schema but leaves most parameters unexplained.

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?

The description clearly states the tool creates a collaboration Mission with specific fields (outcome, acceptance criteria, capabilities, optional reward) and distinguishes it from sibling tools like create_bounty_draft. However, it doesn't explicitly name siblings or contrast with apply_to_mission/submit_mission, so it loses a point for not fully differentiating.

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 description implies usage by mentioning what a Mission is and the reward caveat, but it doesn't provide explicit when-to-use vs alternatives. It mentions the API key requirement, which is a prerequisite but not usage guidance. With siblings like browse_missions and apply_to_mission, explicit context would help. The description is adequate but leaves the agent to infer when this tool is appropriate.

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