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

With no annotations, the description carries the full burden, and it does substantial work: it discloses the crash-resume value proposition, that the live instance includes the full payload + commitment + submit instructions, and crucially that resuming 'without consuming an attempt' avoids a side effect. It doesn't cover rate limits or whether calls mutate run state.

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 description is front-loaded with a 'When to use' label and then a dense second sentence heavily loaded with parentheticals. It's information-rich but the parenthetical stacking (input + commitment + submit instructions) and the parenthetical about attempts make it harder to parse than it needs to be.

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?

No output schema exists, so the description must describe return values, and it does reasonably well: per-class state, scores, attempt counts, and the live instance's full payload. For a read-only status tool with one optional param, this covers the essential behavior.

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 100% and the parameter description already explains the optional run_id with its default. The description adds nothing parameter-specific, so baseline 3 applies. It relies entirely on the schema for the single parameter.

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?

Names a specific verb+resource (get trial status/poll your trial run) and clearly distinguishes itself from sibling list/get tools by scoping to the caller's recent trial runs. It doesn't explicitly name which sibling tool to use instead of it, leaving some ambiguity versus get_status or get_job.

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?

Opens with an explicit 'When to use: Between trial submissions', giving real context. It doesn't state when NOT to use it or which sibling (e.g., get_status) to prefer for other polling needs, so it stops short of full routing guidance.

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