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

Annotations already declare readOnly/idempotent/non-destructive and closed-world, so the safety profile is covered. With no output schema, the description adds real value by specifying the payload contents (the full metric list), which the agent could not otherwise know.

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?

Two sentences, front-loaded with the core verb and payload, with the index guidance appended. No padding, though the trailing note partially restates what the schema already lists.

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?

Given one optional parameter, full schema coverage, and no output schema, the description supplies what the schema cannot: the shape and breadth of the returned per-stock record. A short note on default index behavior or sort order would make it complete.

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 description coverage is 100% and the schema itself enumerates every index slug, so the description is not required to carry parameter meaning. It adds only a light grouping hint ('Nifty broad, size and sector indices plus Sensex'), which is marginal over the schema.

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?

States a specific verb+resource with scope ('stock heatmap for an index — all constituent stocks') and enumerates the exact metrics returned (market cap, PE, PB, multi-horizon price changes, volume, sector). That distinguishes it cleanly from sibling index tools like get_index_performance or get_market_data.

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 use case (view all constituents of an index at once) and points the agent to the index parameter for available values, but it never states when to prefer this over get_index_performance, scan_movers, or get_market_data, nor any exclusions.

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