get_52_week_breakouts

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

With no annotations, the description must carry the behavioral disclosure. It reveals the 'today (NSE)' time/market scope and the 'which' selection, but does not describe default behavior for the high/low choice, limit handling, sorting, or output format. Adequate for a simple list but with meaningful gaps.

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 two short sentences with no filler; the core resource and the key parameter are front-loaded. Every part earns its place.

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 description covers the essential selection and market, but with no output schema and no annotations it omits return shape and limit behavior. Enough for an agent to attempt the call, but not fully self-sufficient.

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 description coverage is 0%, so the description must explain parameters. It adds meaning to 'which' by specifying high | low, but it never explains 'limit' or how it affects results. Only one of two parameters receives semantic support.

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 states a specific resource (stocks hitting new 52-week highs/lows on NSE) and the selection parameter (which: high | low). The verb and market scope distinguish it clearly from siblings like get_top_movers or screen_stocks, so an agent can tell what it does.

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?

It gives clear context for when to call it: when you need today's NSE 52-week breakout stocks. It does not explicitly name alternatives or exclusion criteria, but the scope is specific enough that confusion with siblings is unlikely.

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