chainscout_intelligence

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

No annotations provided, but description fully discloses behavior: refresh every 15 minutes, lists endpoints (/whales, /trending, etc.), and format of whale_alerts output. Exceeds annotation 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?

Front-loaded with key purpose, uses brief sentences, no filler. Every sentence adds value (purpose, use cases, refresh rate, endpoints).

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 parameterless tool with output schema, description fully covers input, behavior, use cases, refresh schedule, and extra endpoints. No gaps identified.

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?

No parameters (0 params, 100% schema coverage), so baseline 4 applies. Description does not need to add param info; schema already sufficiently covers empty input.

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?

Clearly specifies it provides on-chain intelligence for Base and Ethereum, listing specific data points (whale_alerts, dex_volume_24h, gas_price_gwei, TVL rankings). Distinct from siblings like whale_alert by covering multiple data types and chains.

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?

Explicitly states use cases: monitor large wallet movements, spot DEX volume spikes, track DeFi protocol health. Lacks explicit when-not-to-use or alternatives, but siblings list provides context.

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