think_submit

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

With no annotations, the description carries the full burden. It usefully discloses validation-on-submit, the error-list-on-failure contract with a retry path, and that the LLM quality audit is advisory and cannot change status. It omits whether submission terminates/mutates session state, idempotency, and permission needs.

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 tight sentences that front-load the core action (submit) and then layer failure handling and the quality-audit caveat. No filler, though the third sentence's conditional framing adds length without operational detail.

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 not explaining return values is acceptable, and the description does cover the error and advisory-audit branches. The gap is on the input side: it never tells the agent how to construct the payload it will be judged on.

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% for both parameters, and `response` is a free-form nested object with additionalProperties=true. The description says the structure is validated but never explains what structure is expected or that it must come from a template (e.g. via think_list_templates) — the single most important thing an agent needs here.

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 clear verb+resource: 'Submit the JSON response for a session', with the added scope of validation and result formatting. It does not, however, distinguish itself from the sibling think_verify_submit, which by name implies a similar submission flow.

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 by the retry loop ('if the structure is wrong... fix it and submit again'), which tells the agent this is the terminal submit step. But it never says when to prefer it over think_verify_submit or how it relates to think_status, and no prerequisites are given.

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