Extract the 10-character PAN embedded in a GSTIN (positions 3-12, 1-indexed). Throws if the GSTIN is the wrong length or the embedded PAN is malformed. Does NOT verify the check character — use validate_gstin for that.
| Name | Required | Description | Default |
|---|---|---|---|
| gstin | Yes | 15-char GSTIN. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses that it throws on wrong length or malformed PAN, and that it does not verify the check character. No annotations provided, but description fully covers behavioral aspects.
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, front-loaded with main action, no redundant information. Every sentence adds value.
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 low complexity (1 param, no output schema), description covers input constraints, edge cases, and relationship to sibling tools comprehensively.
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 100% but parameter description is minimal. Description adds meaningful context about extraction positions and error conditions, exceeding baseline of 3.
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?
Description clearly states it extracts the 10-character PAN from a GSTIN (positions 3-12, 1-indexed). Distinguishes from siblings like validate_gstin by specifying what it does not do.
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 says 'Does NOT verify the check character — use validate_gstin for that', providing clear when-not-to-use and a specific alternative tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: extracting PAN, resolving state, and full validation. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case (extract_pan, state_from_gstin, validate_gstin).
Three tools is slightly below typical range but well-scoped for a focused validation server; each tool is essential and not redundant.
Covers the main validation needs (format, state, PAN, check digit). Minor gaps like a dedicated check-digit tool or batch processing exist but are non-essential.