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

Annotations declare readOnlyHint=false and destructiveHint=false, so the write/non-destructive profile is already covered. The description adds genuinely new behavioral context beyond that: the submission lands in a review queue and produces no public post or task, which is the key side-effect fact an agent needs. It stops short of any permissions, rate-limit, or retry semantics, so it is not 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?

One sentence, front-loaded with the core action and immediately followed by the outcome constraint; no filler or repetition of the title. It is arguably too terse for a 6-parameter write tool, but as pure conciseness and structure it is clean.

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 described, and annotations carry the safety profile. But for a 6-parameter write tool with 0% schema description coverage, the description leaves all parameter semantics, idempotency behavior of client_submission_id, and the review workflow (what happens after submission) undocumented — significant gaps for an agent to call it correctly.

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% across 6 parameters with 3 required, so the description carries the full explanatory burden and does not meet it. It says nothing about what 'problem' or 'proposed_experiment' should contain, what 'related_targets' references (article/topic SubmissionRefs), or that 'client_submission_id' is presumably a deduplication key. Only a loose mapping from 'project idea' to the required fields is implied.

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 (submit a project idea) plus the governing process (editorial review), and explicitly scopes the outcome: no public post, no task. That negative scoping is exactly what separates it from write-oriented siblings like add_map_content, create_topic_at_position, and publish_study_path.

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?

The description implies the use case (propose rather than publish) via 'never creates a public post or task,' which is useful when-not context. However, it never names an alternative tool or states the condition under which an agent should prefer propose_project over, say, publish_study_path or submit_feedback, leaving routing to inference.

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