get_sebi_alerts

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

No annotations provided, so description must convey behavior. It adds context about severity classification and historical significance, but lacks details on read-only nature, error handling, or rate limits. The description adds some value beyond structural elements.

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 moderately concise but includes a promotional quote and example that add length without critical information. It could be more streamlined while retaining essential guidance.

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 single-parameter tool with an output schema, the description covers purpose and parameter usage. However, it does not describe output format or specify behavior for invalid inputs, leaving some gaps. Generally adequate but not fully comprehensive.

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 input schema only defines the 'sector' parameter with a default. The description expands with examples ('Banking', 'SME/Micro', 'Broking') and clarifies that 'all' provides full report. Since schema coverage is 0%, the description compensates well.

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?

Description clearly states the tool fetches SEBI orders and classifies them by severity and sector, with a purpose of early warning. However, it does not explicitly distinguish from sibling tools, though no sibling seems directly analogous.

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 explicit guidance on when to use this tool versus alternatives. The description implies use for monitoring regulatory actions but does not mention when not to use or suggest other tools, leaving the agent without clear decision context.

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