submit_code

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 validation behavior (syntax-checked), the failure path, and what happens on success (stored and linked as a resource, server retains the last 50). It omits whether resubmission overwrites a prior submission and what an error response looks like.

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?

Three short sentences, front-loaded with the action and artifact, then the timing constraint, then the side effect. No filler and nothing repeated from the 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?

For a single-parameter submission tool with no annotations and no output schema, the description covers purpose, timing, validation, and persistence/retention. Remaining gaps (retry semantics, error format) are minor given the tool's simplicity.

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 0% and the schema itself only says 'code: string', so the description has to define the payload; it does so by specifying the code must be the final, verified, self-contained solver program. It stops short of stating language/format constraints, but the payload's required qualities are communicated.

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 (submit) plus the exact resource (the final, verified, self-contained solver program), which is distinct from the sibling execution/status tools. It does not explicitly name which sibling it is contrasted with, but the artifact it accepts is unambiguous.

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 explicit timing ('Call ONCE at the end'), an explicit prerequisite ('only after executing the program via python_exec and passing your verification'), and names the sibling tool involved. An agent cannot mistake when this should fire.

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