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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds that results are 'dated' and include 'published AI analyst takes', which is useful context, but it does not say anything about freshness, provenance, pagination, or completeness of the research set.

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?

Two short sentences, front-loaded with what is returned and followed by a one-line caveat. No wasted text.

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?

An output schema exists, so return values need not be described, and annotations cover safety. Still missing is any hint of how this differs from the news/context/rules siblings and any explanation of chainId, leaving a real gap for a two-parameter discovery tool.

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 coverage is 50%: address is well documented with a regex, but chainId carries no description in the schema and no mention in the tool description. The phrase 'for a binary market' only faintly implies that address identifies a market and does nothing to explain chainId's role or default.

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 (read) and resource (dated research, sources, AI analyst takes) scoped to a binary market, which is clearly distinguishable from siblings like get_market_news or get_rules. It stops short of explicitly naming the adjacent tools it differs from, so it lands at 4 rather than 5.

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 only guidance is the disclaimer 'Research, not advice', which is a liability statement, not a selection rule. It never says when to prefer this over kellian_get_market_news, get_context, or get_rules, so an agent must infer the boundary.

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