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

Annotations already establish the safe, idempotent, read-only profile, but the description adds real context: the brief is shared and cached with status 503 while regenerating, symbol caps (60 for quotes), downsampling to ~90 points, the 1m period default, limit range 1-30, and the api:read requirement. It stops short of describing failure behavior for the other views or the response shape beyond app_url.

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?

Content is dense and largely earns its place, but it arrives as a single wall of parenthetical prose covering ten views. A per-view list structure would make it far easier to scan; as written it is informative but poorly front-loaded beyond the opening clause.

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?

With no output schema, the description carries the burden of explaining what each of the ten views returns, and it does so. It also notes app_url in the response. What is missing is minimal — pagination/limits on other views and how views behave when data is unavailable.

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 88%, so the baseline is 3, but the description earns more by mapping parameters to views — kind only for asset_description, limit only for news, market only for breadth, period only for series — and by clarifying that crypto means Hyperliquid perps and symbols means US equities, which the schema does not state.

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 resource — the Home Market Brief plus 'the reads behind it' — and enumerates each view, so an agent knows exactly what data is returned. It does not explicitly route against overlapping siblings like get_sentiment, get_news_headlines or get_bars, so the differentiation is implicit rather than stated.

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?

Usage is only implied through the per-view content descriptions; there is no explicit when-to-use/when-not guidance and no mention of which alternative tool to pick when the agent only needs one view. The one real guideline given — 'never mix' equity and crypto for returns/series — is a parameter constraint rather than tool selection guidance.

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