botindex_zora_attention_momentum

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'early signal' and '$0.03,' hinting at cost or value, but doesn't explain what the tool returns (e.g., list of trends, scores), how it calculates momentum, rate limits, authentication needs, or error handling. For a tool with no annotations, this leaves significant behavioral gaps.

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 brief and front-loaded with key concepts ('attention momentum,' 'Zora trends,' 'early signal'), but includes an extraneous detail ('$0.03') that might confuse without context. It's efficient overall, with two sentences that convey the core idea without unnecessary elaboration.

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?

Given no annotations and no output schema, the description is incomplete for a tool that likely returns complex trend data. It lacks details on return format, data freshness, how 'momentum' is defined, and error cases. For a tool named 'attention_momentum' in a crypto/analytics context, more behavioral and output context is needed to be fully helpful.

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?

The input schema has 1 parameter with 100% description coverage ('limit' with default 20). The description adds no parameter-specific information beyond what the schema provides. Since schema coverage is high, the baseline is 3, as the description doesn't compensate but also doesn't detract from the schema's documentation.

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 states the tool identifies 'which Zora trends are accelerating' and calls it an 'early signal for emerging attention markets,' which gives a vague purpose. It mentions 'Zora trends' but doesn't specify what type of trends (e.g., tokens, NFTs, creators) or what 'attention momentum' means operationally. It distinguishes from some siblings by focusing on Zora and momentum, but the purpose remains somewhat abstract.

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 provides no guidance on when to use this tool versus alternatives. It mentions 'early signal for emerging attention markets,' which implies a use case for detecting trends, but doesn't specify scenarios, prerequisites, or compare it to sibling tools like 'botindex_zora_trending_coins' or 'botindex_zora_intel.' Without explicit when/when-not instructions, usage is unclear.

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