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

Beyond the read-only annotations, the description discloses access-tier behavior: without a key or on a free account it returns a limited Free preview of 5 markets, only the analysts' average, and 1 headline, with meta indicating what was withheld. It also explains that Pro accounts include named top traders with side, shares, tier, entry price, and last move.

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 front-loaded and dense, with the key 'one call per market' summary first. It is somewhat run-on due to the long parenthetical field list, but every part communicates useful scope or access behavior, and the disclaimer is brief.

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 the output schema, rich annotations, and 100% schema coverage, the description supplies enough context to call the tool correctly. It covers returned data groups, filtering modes, pagination, and free-tier truncation behavior.

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 description coverage is 100%, so each parameter is already documented. The description adds a lightweight grouping of filter options and pagination, but does not add syntax, defaults, or constraints beyond what the schema provides.

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 a specific resource and scope: every market's research context in one compact record per market, listing the exact data groups returned. It distinguishes itself from single-market siblings by emphasizing 'Every market's research in one call.'

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?

It explains how to filter by segment, category, ids, or all, and how to page with a cursor, but it does not explicitly say when to use this tool instead of siblings like kellian_get_market_research or kellian_list_markets. Usage is implied rather than guided.

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