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

With no annotations, the description carries the full burden and delivers real behavioral context: the list is refreshed daily (staleness expectations), each entry includes a short analysis (return content shape), and callers are obligated to cite the source URL. It stops short of covering auth, rate limits, or size/ordering behavior.

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 tight sentences with the resource and scope front-loaded, followed by a functional attribution instruction. No filler or restatement of the tool name.

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 compensates by stating what each entry contains ('a short analysis') and how fresh the data is. Ordering, result shape beyond the analysis blurb, and filter limits are left implicit, but the essentials for correct invocation are present.

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?

One optional param with 100% schema description coverage, so the schema already documents limit as maximum results 1-25 with a default of 10. The description adds nothing about the limit, so the baseline 3 applies.

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 verb and resource (retrieve Invexia.ai's AI-curated trending stocks list) and defines the selection criteria (momentum, news flow, screening interest). It is easily distinguished from siblings like get_undervalued_stocks or get_valuation_scorecard, which target entirely different cohorts.

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: 'refreshed daily' hints that this is for current, momentum-driven names rather than historical or valuation-based picks. No explicit when-not guidance and no sibling alternatives (e.g., get_stock_snapshot for a single name) are named.

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