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

No annotations are provided, so the description fully bears the burden. It discloses real-time, pay-per-call nature, classification by event type, and sentiment tagging. It does not mention rate limits or data freshness details, but the key behavioral traits are adequately covered.

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 sentences, front-loaded with the core purpose, and every sentence adds value. There is no fluff or repetition, making it highly efficient.

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?

No output schema exists, but the description explains the return format: announcements classified by event type, sentiment, and impact summary. This is fairly complete given the tool's purpose. Minor gaps like pagination or maximum limit are acceptable for real-time data.

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 coverage is 100%, so baseline is 3. The description adds meaning by explaining 'limit' as 'how many recent announcements' and 'symbol' as 'Optional NSE symbol filter', complementing the schema descriptions with clarity on usage.

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 it provides 'Live NSE corporate-announcement intel' for Indian companies, with specific event types listed. The verb 'intel' implies data retrieval, and the resource is announcements, distinguishing it from sibling tools like hsh-india-fundamentals.

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 the tool is for fetching corporate announcements with optional symbol filter, but does not explicitly state when to use it versus alternatives (e.g., for fundamental data vs announcements). No exclusions or prerequisites are mentioned.

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