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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions 'Daily NAV' implying a read operation, but does not disclose any behavioral traits such as date format expectations, error handling, rate limits, or whether the response includes additional metadata. For a tool with zero annotation coverage, this is insufficient.

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, well-structured sentence that immediately conveys the tool's purpose. Every word contributes meaning, and there is no extraneous information. It is appropriately concise given the tool's simplicity.

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 low complexity (2 parameters, no output schema, no annotations), the description should be more complete. It does not mention what the output looks like (e.g., return format, fields), error scenarios, or any constraints like date range limitations. A user would need additional documentation to understand the tool fully.

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 input schema has 0% description coverage, so the description must compensate. It adds meaning by indicating that 'scheme_code' identifies a mutual fund scheme and 'date' is likely optional (implied by 'Daily NAV'). However, it does not specify expected formats for either parameter, and 'Daily NAV' suggests date might be optional but does not confirm default behavior. The description provides basic semantic help but lacks precision.

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 daily NAV for an Indian mutual fund scheme by AMFI scheme code. It specifies the resource and action, making the purpose clear. While it does not explicitly differentiate from sibling tools, those tools are in unrelated domains (GST, RBI, SEBI), so confusion is unlikely.

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?

No guidance on when to use this tool or when to consider alternatives. There is no mention of prerequisites, limitations, or context for choosing this tool over others. The description only states what the tool does, not how to use it appropriately.

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