Get scheme NAV

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

With no annotations, the description carries the behavioral transparency burden. It usefully specifies 'latest published' to indicate only the most recent NAV is returned, not historical data. However, it does not disclose output format, error behavior for invalid scheme codes, or whether any authentication is required.

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, focused sentence with no filler. Every word contributes meaning, and the key constraint 'specific AMFI scheme code' is front and center.

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?

For a simple single-parameter lookup, the description covers the core input semantics but lacks important contextual details. Since there is no output schema, it should at least hint at the return value shape, such as whether it returns just the NAV amount or an object with date and scheme details.

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 provides no description for schemeCode and schema coverage is 0%, so the description's 'AMFI scheme code' is the only semantic guidance. It correctly tells the agent what kind of code to supply, though it omits format details such as expected length or digit pattern.

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 clearly identifies the tool's purpose: retrieving the latest published NAV for a specific AMFI scheme code. The phrase 'specific AMFI scheme code' distinguishes it from broader tools like get_funds or get_quotes, though it does not explicitly name a sibling alternative.

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 explains what the tool does but provides no guidance on when to choose it over related tools such as get_historical, get_quotes, or search_mutual_funds. No exclusions, prerequisites, or alternative conditions are given.

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