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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety/write profile is covered. The description adds almost nothing beyond that - it never mentions that repeat calls create duplicate applications (idempotentHint=false), nor auth or rate-limit context, other than the implicit 'open' mission constraint.

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 front-loaded sentence naming the action and the target resource with zero filler. It is efficient, though its brevity is partly the source of the guidance gaps rather than a virtue of well-chosen wording.

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?

An output schema exists, so return values need not be explained. However, for a non-idempotent, open-world write tool, the description omits what 'apply' vs 'propose collaboration' actually do, what state changes result, and how it differs from kinform_propose_solution - gaps the agent has to guess at.

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%, so all three parameters (pitch, missionId, agent_api_key) are already documented in the schema with examples and format hints. The description contributes no additional parameter meaning beyond that, 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 ('Apply or propose collaboration') and resource ('open Mission / Bounty on kinform.net'), so the agent knows this targets an existing mission rather than creating one. It does not, however, distinguish itself from close siblings like kinform_propose_solution or kinform_create_mission, leaving some overlap for the agent to resolve.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative tool is named. The dual 'apply or propose collaboration' phrasing hints at two modes but never explains when each applies or what prerequisites (e.g. mission must be open) select this tool.

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