get_pcr

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

Discloses fallback mechanism (NSE first, then Upstox) but no annotations exist to carry burden. Missing details on error handling, data freshness, or what happens if both sources fail.

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 action, no superfluous words. Efficient and direct.

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?

Adequate for a simple 0-param tool: covers purpose, source fallback. Lacks output format description or limitations (e.g., only Nifty 50). Could be more complete but acceptable.

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?

No parameters exist, so baseline is 4 per rules. Description adds no param info, but schema coverage is 100% (empty).

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?

Clearly states verb 'Fetch', resource 'Put-Call Ratio (PCR) for Nifty 50 options', and distinguishes from sibling tools (e.g., get_chart_data, get_fii_dii_data) by being specific to PCR.

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?

Implies usage context (fetching PCR) but provides no explicit guidance on when to use or avoid, no mention of alternatives or prerequisites. Suggests fallback behavior but lacks situational direction.

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