get_most_active

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

With no annotations, the description carries the full burden. It discloses that data is for today and NSE, but does not explain whether the data is real-time, end-of-day, how 'most active' is computed, or any limits/quirks. This is a short read-only-type query, but behavioral details are minimal.

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, front-loaded sentence that wastes no words. It could be more structured by adding parameter guidance, but for an overview it is appropriately concise.

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 no output schema, no annotations, and zero parameter descriptions, this description is too thin for reliable invocation. An agent missing the schema and defaults would not know exact parameter values or what response to expect. It is minimally useful but not complete for autonomous use.

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 has 0% parameter description coverageage, so the description must compensate. It partially does: 'by traded value or volume' explains the purpose of the 'by' parameter. However, 'limit' is not described, and the exact accepted values for 'by' are not spelled out. The defaults help but do not fully clarify semantics.

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 identifies a specific resource: most actively traded stocks today, by traded value or volume, limited to NSE. This is a clear verb+resource pairing, though it doesn't explicitly distinguish itself from sibling tools like get_top_movers.

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?

No guidance is given on when to use this tool versus siblings such as get_top_movers or get_market_pulse. The description implies a use case (most active stocks) but does not state conditions, exclusions, or alternatives.

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