get_most_active

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 transparency. It only states the basic action and metric but omits details such as the time period, sort order, number of results, or output format. This leaves the agent uncertain about what exactly will be returned and how the result is structured.

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 a single, focused sentence that is front-loaded and contains no extraneous information. Every word contributes to conveying the tool's purpose.

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 tool is simple with no parameters and no output schema, so the description is expected to explain return values. It says 'most actively traded stocks by volume' which suggests a list, but does not specify the number of stocks, format, or whether it includes quotes, tickers only, or other data. It is adequately complete for a basic list tool but lacks additional contextual details.

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 tool has zero parameters, so parameter semantics are trivially clear. The baseline of 4 applies, and the description does not need to explain any parameter meanings. It adds no unnecessary parameter-related information.

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's purpose with a specific verb ('Get'), a specific resource ('most actively traded stocks'), and a defining criterion ('by volume'). This distinguishes it from sibling tools like get_market_gainers or get_sector_performance, which focus on different market metrics.

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 when to use the tool (when needing the most actively traded stocks by volume) but offers no explicit guidance on alternatives or exclusions. It does not mention when to prefer this over get_market_gainers or other market data tools, leaving usage context largely inferred from the name and description.

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