get_mutual_fund_nav

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

No annotations provided, so description carries full burden. It describes the tool as retrieving 'latest live NAV', implying a read operation with near-real-time data. No side effects or limitations mentioned, but the activity is straightforward and the description is sufficient for such a simple tool.

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 with no wasted words. First sentence states purpose, second provides usage context and a prerequisite. Front-loaded and efficient.

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 one parameter and an output schema, the description covers the essential usage: purpose and how to obtain the input. It could mention that the output is just the NAV, but the output schema handles that. Reasonably complete for a simple lookup 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?

Schema coverage is 0%, so description must compensate. It refers to 'AMFI mutual-fund scheme code' and directs to search_mutual_funds, but does not add further detail about the parameter format or valid values. This is minimal compensation for the lack of schema 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?

The description clearly states it retrieves the latest live NAV for an AMFI mutual-fund scheme code using a specific verb+resource. It distinguishes from sibling search_mutual_funds by specifying that the scheme code must be found first.

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?

Explicitly states it is used for 'what's the current NAV of fund X', and instructs to first use search_mutual_funds to obtain the code. This provides clear context and a prerequisite.

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