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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, but the description adds real context beyond them: the operation enqueues to a durable queue (asynchronous, persisted), the packet is user-owned, and a personal paid API key is required. The phrase 'read-only ... WorkPacket' slightly risks being misread as a read-only tool despite readOnlyHint=false, but grammatically it modifies the packet, not the tool, so it is not an annotation contradiction.

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?

Two tightly packed sentences with the action and the auth constraint front-loaded and no filler. It loses a point for jargon density that pushes explanatory content out rather than for verbosity.

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 two-parameter submission tool with no output schema, the description should say what a successful call yields (a task identifier/receipt) and that results and cancellation happen via get_task_result and cancel_research_task. It covers the safety and auth profile reasonably but leaves the async lifecycle, which is the operator's most likely point of confusion, undocumented.

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%, so the description carries the full burden of explaining the two parameters and does not do so at all. The 'prompt' length window and especially the 'engine' enum values ('source' vs 'auto') are left entirely opaque, which matters because that enum choice likely changes which backend the research runs on.

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?

The description names a specific verb ('Submit') and a specific resource ('market research WorkPacket') delivered to a named durable queue, so the action is distinguishable from cancel/result siblings. It does not explicitly say which sibling to use for other research types, and proprietary terms like 'WorkPacket' and 'SignalForge' are undefined, but the core purpose is unambiguous.

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 only guidance is a prerequisite ('Requires personal paid SignalForge API key'), which tells the agent who may call it, not when it should choose this over research_prediction_market, market_snapshot, or other siblings. No when-not conditions, no mention that the prompt maxes at 900 characters, and no note that the task must later be retrieved or cancelled elsewhere.

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