stocklist

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals the default sort order (one-day change descending), the lightweight nature of rows, and the inclusion of company_info fields (report date, market cap). This provides meaningful context beyond what the schema shows, though it does not explicitly state whether the operation is read-only (which is obvious from context).

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 compact and front-loaded with the main purpose in the first sentence. It uses three concise sentences to convey purpose, default behavior, and row structure without any extraneous information. Every sentence adds value.

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?

Given that there is no output schema, the description provides a useful summary of the return rows (lightweight snapshots plus company_info). It covers default sorting and the risers_only filter. However, it does not mention how the limit parameter works, other possible sort attributes, or pagination, leaving some gaps in a simple list context.

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?

The schema description coverage is 0%, so the description must compensate. It explains the risers_only parameter and the default sort attribute (one-day change/descending), but it does not explain the 'limit' parameter or valid values for 'sort_order' and 'sort_attribute'. The description adds partial clarity but leaves gaps for several parameters.

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 the tool provides a 'Market overview list of stocks' with specific categories (risers/fallers, most traded). It uses a specific verb (list) and resource (stocks), and its focus on a broad market overview distinguishes it from sibling tools like stock_profile or chart, which target individual instruments.

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 market-wide overviews and mentions how to filter for risers (risers_only=true), but it does not explicitly compare with alternatives or state when not to use this tool. The lack of explicit exclusions or alternative tool references makes the guidance only implied rather than definitive.

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