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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by enumerating exactly which duty components come back (BCD, SWS, AIDC, IGST, anti-dumping, MIP, policy, compliance notes) and naming the data maintainer, which is meaningful for a tool with no output schema.

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?

A single front-loaded sentence that opens with the verb and resource before listing returned fields. The long duty-component enumeration is justified because there is no output schema, and nothing in the sentence is filler or redundant with the annotations.

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 one-parameter, read-only lookup with no output schema, the description supplies the scope, return contents and data provenance an agent needs. Minor gaps remain: it does not say what happens for an unknown or non-China-origin code, nor how current the duty rates are, both of which would matter for a compliance lookup.

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% for the single hs_code parameter, and the schema already specifies the 8-digit ITC-HS pattern with an example. The description restates the domain constraint ('8-digit ITC-HS code') and adds the China-import scope, but contributes no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Returns the Indian customs duty profile for an 8-digit ITC-HS code') and narrows the scope to goods imported from China. The 8-digit lookup framing separates it cleanly from search_hs_code, which implies keyword-based discovery, without the agent needing to open either schema.

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?

Usage is only implied by the scoping ('8-digit ITC-HS code', 'imported from China'), which does tell an agent it needs an exact code rather than a keyword. However, it never names search_hs_code as the tool to use when the code is unknown, nor estimate_landed_cost for downstream cost calculation, and states no exclusions (e.g. non-China origins are out of scope).

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