pyth_stream_prices

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

No annotations, so the description carries the full load. It does disclose the essential operational model — live streaming, collection over a bounded window, up to 100 feeds — which is real behavioral context beyond the name. It omits auth/rate-limit requirements, termination semantics, and what actually comes back from the stream, so a significant gap remains.

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?

One front-loaded sentence with zero filler — scope limits land immediately after the verb.

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 four-parameter streaming tool with no annotations, no output schema, and 0% parameter documentation, the description leaves the agent unable to predict behavior or set threshold/max_updates correctly. Adequate for identifying the tool, not for invoking it with confidence.

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%. The description only gestures at 'feeds' (up to 100) and, loosely, duration_ms via 'bounded duration'; the meaning of threshold (0-100) and max_updates is left entirely to inference from bare integer types and bounds. With four parameters and no schema prose, this is a substantial compensation 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?

States a specific verb ("Stream") and resource ("live Pyth price updates from the Hermes streaming endpoint") with scope (up to 100 feeds, bounded duration). That verb distinguishes it in practice from the snapshot siblings pyth_get_price/pyth_get_prices, though no sibling is named explicitly.

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?

Usage is only implied: 'streaming' plus 'bounded duration' signals the case where you need a window of live updates rather than a one-shot quote. No explicit when-to-use, when-not-to-use, or alternative named, and the sibling list contains the obvious alternatives the agent must choose between unaided.

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