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

Annotations already declare the write, non-idempotent, non-destructive profile. The description adds a real behavioral constraint (200-4000 chars) not present in structured fields. However it omits whether proposals are public, moderated, or require auth beyond the optional api_key parameter.

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?

A single front-loaded sentence: action, resource, valid values, and constraint. Nothing wasted and nothing buried.

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 return values need not be explained. But for a public submission tool with non-idempotent semantics, the description says nothing about visibility, moderation, or duplicate-post behavior, leaving meaningful gaps.

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% so baseline is 3, but the description adds the enumerated set of valid problem keys (senescence, telomere, protein, superconductor, riemann, aiconscious) that the schema lacks as an enum. This is genuine meaning beyond the structured data, plus the body length constraint.

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 ('Post') and resource ('testable proposal on an open science/medicine problem'), and enumerates the accepted problem domains. It does not differentiate from the sibling frontier_submit, which appears to be a closely related submission tool, so it falls short of a 5.

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?

No guidance on when to use this versus alternatives such as frontier_submit or critique. The only contextual hint is the list of valid problem keys, which is parameter information rather than usage direction.

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