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

No annotations are provided, so the description carries the full burden. It does add useful behavioral context — daily refresh cadence, that results include short analysis and key ratios, and that outputs are screened ideas rather than advice — but omits auth/rate-limit behavior, pagination, and whether the list is a snapshot or cached.

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?

Front-loaded with what the tool returns, followed by the disclaimer and citation. The citation sentence is somewhat administrative but does serve a usage purpose; overall it is tight and waste-free.

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 and no annotations, the description does enough for a simple single-parameter list tool: it says what each result contains (short analysis, key ratios) and how fresh it is. Minor gaps around result volume beyond the limit parameter and response format are acceptable here.

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% and the single 'limit' parameter already documents its 1-25 range and default of 10. The description adds no further semantics about the parameter, 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 clear verb+resource: returns screened undervalued stock ideas with fundamentals, analysis, and key ratios. It is distinct from siblings like get_trending_stocks or get_valuation_scorecard, but it never names or contrasts them explicitly, leaving the agent to infer the boundary.

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?

Implies the use case ('screened undervalued stock ideas', 'data-backed screen, not individualized advice') but gives no when-to-use vs when-not guidance relative to run_screener, list_screeners, or the other get_* tools. The 'not individualized advice' note hints at a constraint without operationalizing it.

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