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

The readOnlyHint annotation already indicates a safe read operation, and the description adds useful context about the output: the number of stocks (5), the ranking metric (Martingale Score with 0-5 scale), and the additional Startingale readings. This goes beyond the annotation without contradicting it.

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 two sentences long and front-loaded with the primary action. Every clause adds relevant detail, with no redundant or filler content.

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?

The description covers the core aspects: what is returned (top 5 stocks), the ranking metric, and the associated reading. The absence of a time period or market specification is a minor gap, but for a simple zero-parameter overview, it is sufficiently complete, especially with the readOnlyHint annotation.

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?

There are zero parameters, so the schema provides no parameter details. The description adds meaning by explaining what the tool returns, which is the relevant information for a no-parameter tool. Baseline for 0 params is 4, and it is well-served.

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 verb ('Get') and resource ('overview of the stock market'), and provides concrete details: top 5 stocks ranked by Martingale Score (0-5) with Startingale readings. This clearly distinguishes it from siblings like crypto_overview or list_top_stocks.

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 implies usage for obtaining a stock market overview with specific ranking criteria, but it does not explicitly mention when to prefer this over alternatives such as list_top_stocks or market_overview. It offers no exclusions or direct comparisons, so guidance is only implicit.

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