nifty_pcr_trend

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

With no annotations, the description details the outputs: PCR by expiry, overall sentiment, and OI data. It clearly indicates it's a read-only data retrieval tool. However, it could mention potential limitations like data freshness or rate limits.

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 well-structured with a clear purpose, list of outputs, args, and examples. It is slightly verbose but each sentence adds value.

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 an output schema exists, the description does not need to detail return format. It adequately covers purpose, parameters, and usage examples. Missing detail on data update frequency or limitations, but overall 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?

The schema has 0% coverage, but the description fully explains the only parameter 'num_expiries' with its default value and purpose. This compensates completely for the schema's lack of description.

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?

Description clearly states the tool calculates Nifty PCR trend across multiple expiries as a market sentiment gauge, which is a specific verb+resource. It distinguishes itself from siblings, as no other tool computes PCR trend.

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 mentions it's a free alternative to Sensibull Pro, but does not explicitly state when to use or avoid this tool versus alternatives. Examples are provided but without exclusive conditions.

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