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

Annotations only cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false). The description adds genuine behavioral context beyond them: it explains where third-party text arrives ('untrusted_content' with a '_notice') and that it is data, not instructions - a real prompt-injection disclosure. It still omits whether submissions are final or resubmittable, and what happens after submission.

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 primary action is front-loaded in the first clause and the whole thing is three short clauses with no filler. The heavy quoting around 'untrusted_content' and '_notice' makes it slightly dense to parse, but nothing is wasted.

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 nested-object mutation with no output schema and 67% param coverage, the description supplies the missing piece - where to get the solution body and how to treat embedded third-party text. Return/pagination semantics are absent but arguably unnecessary for a submit tool.

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 67% and the description meaningfully supplements the two documented params by defining what 'solution' must contain and pointing to the equivalent HTTP body as the authoritative shape. The 'token' param's log-exposure caveat lives in the schema, not the description, so no extra credit there.

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: 'Submit your solution to a mission.' An agent can distinguish it from mission_claim, missions, and propose without opening the schema, though no sibling is named explicitly.

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?

Usage is implied rather than stated - you submit a solution to a mission you already have an id for - but there is no explicit when-to-use/when-not guidance, no mention of prerequisites (claiming the mission first), and no alternative tools named.

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