get_sebi_alerts

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

With no annotations, the description carries full burden. It discloses that the tool fetches and classifies orders, and adds predictive context about severity preceding corrections. However, it omits operational details such as data freshness, output structure, or limitations, which would improve transparency.

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 front-loaded with a clear purpose, followed by a practical example and parameter documentation. The illustrative quote is slightly extra but adds context without bloating the description. Overall, it is concise and well-structured.

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?

For a simple one-parameter tool with an output schema (not shown), the description adequately covers the purpose and parameter usage. It lacks details about update frequency or data source, but these are not critical given the tool's simplicity and the presence of an output schema.

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 no descriptions (0% coverage), but the description comprehensively explains the 'sector' parameter with concrete examples ('Banking', 'SME/Micro', 'Broking') and the use of 'all' for a full report. This fully compensates for the schema gap.

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 fetches recent SEBI orders and classifies them by severity and sector, with a specific verb ('Fetches') and resource ('SEBI orders'). It differentiates from sibling tools like sec_filing (SEC) by focusing on SEBI enforcement order tracking.

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 frames the tool as an 'early warning before regulatory crash' and mentions historical impact on stock corrections, providing clear context for when to use it. However, it does not explicitly exclude alternatives or name sibling tools for comparison.

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