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

Annotations already indicate a write (readOnly=false) and non-destructive, open-world operation. The description adds substantive traits beyond that: dedup logic by source_url or similar title within 30 days, moderation via pending/admin approval, a 5-credit cost, and an account requirement. This is rich operational context an agent cannot get from annotations.

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?

Purpose is front-loaded in the first sentence, followed by dense constraint clauses (format, dedup, moderation, cost, account). Every clause carries actionable information with no filler.

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 9-param, no-output-schema submission tool, the description covers format rules, dedup, moderation workflow, cost and account prerequisites, which is most of what an agent needs. A few optional params (tags, author_name, featured_image_url) remain unexplained, but they are non-blocking for correct invocation.

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 67%, so the schema documents several params (title, content, excerpt, categories, source_url, startup_slug) while tags, author_name and featured_image_url are bare. The description reinforces content length, controlled categories, and source_url dedup role, adding some meaning, but it leaves several parameters unaddressed — a baseline 3.

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 (Submit) and resource (news article / press release), which is enough to distinguish it from the funding, product, patent and research submission siblings. It doesn't explicitly name those alternatives, but the resource is precise enough that an agent can route to it without ambiguity.

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?

Prerequisites are given (dedup within 30d, costs 5 credits, needs a free StartupHub.ai account, lands in pending), which is useful context. However, there is no explicit when-to-use-or-not guidance relative to sibling submit_* tools, so usage is only implied by the resource type.

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