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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered and the description does not contradict it. The description adds genuine context about result composition (verdicts, this week's biggest score changes). It says nothing about sort order, how the limit is applied, or whether the weekly change section appears for every sector.

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 sentences, no filler, with the primary output front-loaded and the sibling reference placed after it. Every clause adds information the agent would otherwise have to guess.

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?

For a read-only two-parameter tool with no output schema, the description reasonably conveys the return shape (ranked companies, valuation verdicts, weekly score changes). The gaps are the semantics of limit and the sort/pagination behavior, which an agent needs in order to size and interpret the response correctly.

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 only 50%: 'sector' is documented in the schema with examples, while 'limit' has no description in either place beyond default/min/max constraints. The description never explains what limit counts (companies returned?) or whether the ranking is descending by score, so the undocumented parameter is left entirely to inference.

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 names a specific output: top companies in a sector ranked by TradeApes health score, plus valuation verdicts and weekly score changes. That clearly separates it from get_score_card, get_valuation and search_tickers. The verb is only implicit ('top companies'), but the resource and ranking basis are unambiguous.

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 supplies a concrete prerequisite and explicit sibling routing: 'Use list_sectors for valid sector names', which prevents a guess-a-name failure mode. There are no when-not conditions or alternatives for retrieving a single company's score, but the guidance that exists is actionable.

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