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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: pagination behavior, the exact content of each page, the data source, the MIT license, and no-auth requirement. This exceeds what the structured fields alone communicate.

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?

Three tight sentences front-load the core purpose, then add return content, use case, alternative routing, and metadata. Every clause earns its place; there is no filler or repetition of schema details.

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?

This is a simple read-only listing tool with 2 optional parameters and an output schema present. The description covers what it returns, why you'd use it, the sibling alternative, the data source, license, and authentication status. Nothing an agent needs to select and call it correctly is missing.

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 description coverage is 100% — both 'page' and 'per_page' have descriptive text with defaults and ranges in the schema. The description only reuses the word 'Paginated' and does not add new parameter-level meaning beyond what the schema already provides, so the baseline 3 is appropriate.

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 states a specific verb ('list'), a concrete resource ('all 37,000+ AMFI-registered India mutual fund schemes'), and the returned fields ('scheme codes, names, and ISIN identifiers'). It clearly distinguishes this bulk-enumeration tool from mfapi.schemes.search by naming the alternative explicitly, so an agent can tell them apart immediately.

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 explicitly tells the agent when to use this tool ('bulk enumeration or building fund directories') and when not to ('Use mfapi.schemes.search for keyword-based lookup instead of iterating all pages'). This is a clear when/when-not with a named alternative, leaving no inference needed.

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