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

With no annotations at all, the description carries the full burden; it does disclose that submissions feed an automated crawler pipeline for cross-platform consensus investigation, which explains the downstream effect. It says nothing about authentication, whether the call is synchronous, whether an ID is returned, or rate limits — notable gaps for a write tool.

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 with no padding; the verb and resource come first. Slightly heavy on product-specific jargon ('SaidItHere's automated crawler pipeline') that an agent gains little from.

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?

Three flat params and no output schema keep it simple, but for a submission/mutation tool with zero annotations the description omits the key unknowns: what is returned after submission, whether duplicates or failures are handled, and what permissions apply.

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 the baseline is 3. The description's enumeration of friction/dilemma/gotcha content loosely informs what problem_description should contain but adds no syntax or length guidance beyond the schema.

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?

Uses a specific verb (submit) plus a well-scoped resource (new software friction / developer dilemma / tool gotcha) and names the destination pipeline. That clearly separates it from the read-oriented siblings get_problem and search_problems, though the differentiation is only implicit.

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 word 'new' hints that this is for fresh submissions rather than existing problems, which weakly implies when to use it over get_problem/search_problems. There is no explicit statement of when not to use it, whether duplicates are rejected, or what to do instead for retrieval.

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