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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered. The description adds genuine behavioral context beyond them: data is measured not forecast, is not a causal claim, covers exactly ONE announcement, and contains no recommendations or price targets. That is meaningful framing for interpreting results.

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 core purpose and dependency come first, which is good, but the description sprawls into marketing/policy filler ('no other Indian data source publishes it', 'MarketPing publishes no buy/sell recommendations, no price targets and no IPO grey-market premium'). Those sentences do not help an agent select or invoke the tool.

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?

There is no output schema, so the description carries the return-value burden and does so thoroughly, enumerating each measurement window and the excess calculations. Combined with the prerequisite note, an agent has enough to call it correctly, though the enumeration is verbose rather than structured.

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?

There is a single parameter with 100% schema description coverage ('Alert UUID from recent_alerts'). The description repeats the same sourcing hint but adds no format or validity detail beyond the schema, so the baseline 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+resource: measured percentage price moves after one filing announcement, with the exact windows reported. It is clear what the tool returns, though it never names a sibling to contrast against (recent_alerts is only mentioned as a dependency, not as an alternative).

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 an explicit prerequisite and routing instruction: 'Get an alert id from recent_alerts first.' That tells the agent where the required input comes from. It stops short of stating when NOT to use this tool or what to use instead for a different reaction view.

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