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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety is covered. The description adds valuable behavioral context: it is measured data, not a forecast, and it explicitly states that no buy/sell recommendations, price targets, or grey-market premium are provided, going beyond the structured annotations.

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 three sentences with no fluff. The first sentence front-loads the exact output and horizons, the second clarifies data nature and uniqueness, the third gives the prerequisite, and the final sentence sets boundaries. Every sentence 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?

For a one-parameter read-only tool with no output schema, the description fully specifies what is returned (percentage returns over multiple horizons), how to obtain the input (from recent_alerts), and what is excluded (recommendations, targets, grey-market premium). An agent has everything needed to invoke it correctly.

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% and the single parameter alert_id is described as 'Alert UUID from recent_alerts'. The description repeats this guidance without adding new semantic meaning, so the baseline of 3 applies.

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 verb and resource: 'percentage returns at 5 minutes, 30 minutes, 1/2/3/5/7/15 days and 1/2/3 months from the announcement price' after ONE announcement. It distinguishes from siblings by explicitly saying 'measured data, not a forecast' and emphasizing that no other Indian data source publishes it, making the tool's unique purpose clear.

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?

Provides a clear prerequisite: 'Get an alert id from recent_alerts first', which tells the agent exactly what input to use and where to get it. It also implicitly contrasts with forecast tools via 'measured data, not a forecast' and explicitly excludes recommendations, price targets, and grey-market premium, guiding against improper use.

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