Market overview

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds value beyond them by specifying the exact snapshot contents and that figures are 'today's', which sets freshness expectations — notably important since no output schema exists.

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?

A single front-loaded sentence that names the payoff ('Today's Indian market in one call') and then lists contents. Every clause earns its place by describing returned data; no filler or repetition.

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?

With no input params and no output schema, the description carries the return-value burden and does so comprehensively, enumerating every data group an agent would get. Nothing needed to call this correctly is missing.

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 tool takes zero parameters, so the schema baseline of 4 applies. There is nothing for the description to clarify about inputs beyond the implicit assumption that all output is current-market scoped.

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?

Specific verb+resource ('Today's Indian market in one call') followed by an explicit enumeration of the exact data returned: indices, India VIX, NIFTY 50 P/E and P/B, sector rankings, breadth, gainers/losers, FII/DII flows, USD/INR, holidays. This clearly distinguishes it from narrower siblings like get_quote or get_index.

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 phrase 'in one call' implies this is the aggregate alternative to making many individual sibling calls, which is useful implicit guidance. However, it never states explicitly when to prefer this over get_index/get_quote or any conditions/exclusions, so usage is only inferred.

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