hyperd.watch.create

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

No annotations, but description covers key behaviors: webhook_secret shown once, alerts HMAC-SHA256 signed, prepayment $3 USDC, duration defaults, and supported protocols. No contradictions.

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?

Concise and well-structured: states purpose, return values, behavioral notes, pricing, duration, and protocol support in a few sentences. No unnecessary words.

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?

No output schema, but description explains return values (watch_id, webhook_secret) and covers pricing, duration, protocols, and limitations. Complete for this tool's complexity.

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%, but description adds context like 'store secret once', prepayment, and duration defaults which are not in schema. Provides moderate additional value beyond 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?

Description clearly states it subscribes to a continuous watch on a wallet/position, specifies return of watch_id and webhook_secret, and mentions liquidation focus. Differentiates from siblings like watch.cancel and watch.list.

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?

Explains when to use (liquidation watches), notes v1.0 limitations and multi-target reserved for v1.1 Pro tier. Could explicitly mention when not to use, but is clear on context.

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