get_market_pulse

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

No annotations are provided, so the description carries the burden of disclosing behavior. The description is content-focused and implies a read-only retrieval through 'snapshot', but it does not explicitly state that it is a safe read, mention any data latency, or describe what 'market status' precisely means. There is no contradiction, but the behavioral disclosure is only adequate.

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 a single sentence that front-loads its value proposition ('One-call market snapshot') and then lists all components with no filler or redundancy. Every listed item is relevant and informative, making the description both concise and well-structured.

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 the tool has no parameters and no output schema, the description does the essential work of enumerating the return categories, which it does comprehensively. Minor ambiguity remains around 'market status' (open/closed vs. trend) and the exact number or format of sector leaders/laggards, but these are not critical gaps for an agent deciding whether to call this tool.

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 has zero parameters, so the schema is fully covered and there is nothing for the description to explain about parameter semantics. The baseline for 0-parameter tools is 4, and the description appropriately focuses on the output rather than inventing parameter guidance.

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 the resource (market snapshot) and enumerates its specific contents: market status, indices with % change and PE/PB, India VIX, sector leaders/laggards, and FII/DII cash flows. This clearly distinguishes it from siblings like get_index_performance, get_top_movers, and get_fii_dii, which cover only subsets of this 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 opening phrase 'One-call market snapshot' gives clear usage context: use this tool when you want a broad overview of multiple market data points in a single request. It does not explicitly name alternatives or exclusion conditions, but the context is strong enough for an agent to choose it over composing multiple separate calls.

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