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

It discloses that the tool operates over hosted HTTP and that artifact persistence will not work unless invoked through stdio MCP in a checkout, and notes the input/body alias. With zero annotations, this is useful but remains thin; it doesn't state side effects, async behavior, or auth requirements.

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?

The text is extremely short and free of filler, but it substitutes cryptic protocol names for an understandable operation. It is concise rather than appropriately structured, with the most useful line (the alias) buried last.

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?

With seven parameters, no annotations, and many sibling operations, the description omits core semantics like how the run is triggered, cost/timeout implications, and expected return behavior. Even with an output schema, an agent lacks the context needed to invoke this tool safely.

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?

It explicitly clarifies that 'input' aliases 'body', but the remaining six parameters (capability_key, wait, timeout, max_cost, idempotency_key) are unexplained in a schema with 0% description coverage. This minimal hint does not compensate for the gap.

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 references 'hydracept.run-result.v1' and 'hosted HTTP' but never states the operation's verb or what it accomplishes. It reveals an alias but not the tool's core purpose, leaving an agent to infer it from the name and 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?

No when-to-use guidance or alternatives are named; the only context is that artifact persistence requires stdio MCP, which is a constraint rather than a selection guide. An agent cannot determine when to prefer hydracept_run over the many sibling tools.

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