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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and open-world profile is covered. The description adds that content is derived from on-chain events and which event classes appear, but says nothing about freshness, ordering, or how the default limit shapes the response.

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 no filler. The category list is long but each item carries real discriminating information about what news types appear.

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 simple read-only, one-optional-param tool with annotations covering safety and no output schema, this is close to sufficient. Missing are ordering/freshness expectations and any hint that `limit` bounds the number of news items returned.

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 single optional `limit` parameter has full schema constraints (default 20, min 1, max 50) but zero textual description coverage, and the description never mentions it. Schema constraints carry the meaning adequately, so baseline 3 applies with no added semantics from the prose.

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+resource ('Chain news from on-chain events') and enumerates the exact content categories returned: market cap milestones, launchpads, insider clusters, dev sells, bundled launches, daily recap. That enumeration distinguishes it from generic siblings like get_feed or get_launches, though it never names those siblings 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?

The description gives no when-to-use or when-not-to-use guidance and does not contrast this tool with get_feed or get_launches, which plausibly overlap. An agent must infer from context alone which of these feeds is appropriate.

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