submit_answers

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

With no annotations, the description carries the full burden and does well: it discloses that dry_run=True returns only a submission plan (a safe preview), that programming submissions return judge results, and that answers_file avoids re-pasting large JSON. It does not cover failure modes, resubmission/overwrite semantics, or auth requirements, which keeps it from a 5.

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?

Front-loads the submit semantics, then args, then payload examples — a sensible order with little waste. The example blocks are justified by the 0% schema coverage, though 'answers: 上述结构（或它们的列表）' partially repeats the opening sentence.

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 4-parameter mutation tool with no annotations and no output schema, the description covers invocation, payload construction, and the dry-run confirmation loop. It leaves the shape of the dry-run plan and the returned judge results implicit, which the missing output schema makes a real gap.

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 and it does: all four parameters are explained, including the exact per-problem-type JSON shape with worked examples, the list-vs-object distinction for answers, the answers_file path convention and its equivalence to answers, and dry_run's default and effect.

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 ('提交答案') and immediately splits the behavior into two concrete modes: whole-exam submission for objective question types versus per-problem submission with judge-result feedback for programming questions. An agent can tell this apart from the sibling list/detail tools without opening any 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?

Gives actionable routing context: exam_id is sourced from pta_list_exams, large payloads should use answers_file under work/ instead of pasting JSON into the conversation, and dry_run defaults to True so the agent previews a plan before confirming with False. It stops short of stating exclusions (e.g. when not to resubmit or how this relates to pta_submission_detail), so not a 5.

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