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

Beyond the read-only and idempotent annotations, the description discloses that results are backtested, ranked by forecast 90-day excess return, include hit rate and PBO, cap at 5 themes per asset class without padding, and mention the bias caveat. This is rich behavioral context that an agent would not get from annotations alone.

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 useful information, with no wasted filler. It is slightly packed and uses a parenthetical, but remains readable and appropriately sized.

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 still explains what each result includes: ranking basis, hit rate, windows, PBO, and bias caveat. It also notes that no key is needed, giving the agent enough context to invoke the tool confidently.

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 100%, so both parameters are already documented in the schema. The description reinforces asset-class behavior with 'at most 5 per asset class' but adds little beyond the schema's own descriptions, making the baseline 3 appropriate.

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 clearly states it returns published top themes ranked by backtested forecast 90-day excess return, with concrete output attributes. It does not explicitly name sibling tools or contrast itself with theme_journey_subthemes, so it falls just short of a 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?

It gives a clear usage trigger: 'Use when the user asks what to trade or which themes perform.' It does not provide exclusions or point to alternatives such as theme_journey_backtest or theme_journey_subthemes, so it is strong but not complete.

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