get_v1_subtensor_derivatives_event_stream

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

No annotations are provided, so the description must carry full behavioral disclosure. It mentions 'filtered' and 'finalized blocks' but omits details on authentication, rate limits, stream format, or data retention. The claim of 'filters supported' contradicts the empty input schema, leaving behavior unclear.

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 description is concise at five sentences, including unique selling point and pricing. It front-loads the core function and avoids unnecessary elaboration, though price and category may be extraneous for tool selection.

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 streaming tool with no output schema, the description misses key context: how to consume the stream, filter syntax, and what events are included. The mention of filters without schema parameters further reduces completeness.

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?

With zero parameters and 100% schema description coverage, the description adds no parameter information beyond the schema. Per guidelines, baseline is 4 for no parameters, and there is no contradiction or missing info.

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 provides a filtered event stream from finalized Bittensor blocks, with module/event filters supported. It distinguishes itself by capturing events that disappear from public lite-node APIs, which sets it apart from sibling tools like get_v1_subtensor_derivatives_block_metrics.

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 description implies usage for accessing events that are otherwise unavailable, but it does not explicitly state when to use this tool versus siblings like get_v1_btc_derivatives_reorg_stream or other event-related tools. No exclusions or alternatives are mentioned.

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