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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds value beyond them: credit cost, auth prerequisite, and dedup by arxiv_id or doi. It stops short of describing the outcome of a dedup match or whether submissions go through review, so it is not exhaustive.

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?

Telegraphic and front-loaded — purpose first, then linking, dedup, cost, and auth. Every clause carries information, though the fragmented sentence style is terse rather than polished.

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?

For a 10-param write tool with no output schema, the description covers the key non-obvious facts (cost, account requirement, dedup keys). It omits post-submission behavior (moderation/publication) and says nothing about the unlabeled parameters, which keeps it short of fully complete.

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 40% across 10 params, so the description must compensate and only partly does: it explains the dedup role of arxiv_id/doi and that startup_slug is an optional parent link. Fields like sectors, pdf_url, source_url, and publication_date get no added meaning in either place.

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 research paper/preprint) and clarifies the inclusion intent, which cleanly separates it from sibling submit_* tools like submit_patent, submit_news, and submit_product. An agent can identify the right tool without opening the schema.

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?

Gives concrete usage context: a free StartupHub.ai account is required and the call costs 5 credits, plus the dedup key. It does not state when to prefer this over alternatives or what happens if the account/credits are missing, but the operational conditions are clear.

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