Search GSTINs by PAN

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

No annotations are present, so the description carries the transparency burden. It usefully discloses that no taxpayer session is required, which is a meaningful behavioral trait. However, it does not state whether the operation is read-only, describe rate limits, or clarify the exact response structure, leaving some transparency gaps.

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 short, direct sentences carry all necessary information. The first sentence states the core operation, the second adds a use case and an auth prerequisite. There is no filler, repetition, or extraneous detail.

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 single-parameter lookup tool with no output schema, the description covers the main context: scope, purpose, and the absence of a session requirement. It could explicitly note that the result is a list of GSTINs or describe the output format, but 'Find all GSTINs' makes the general shape inferable.

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% and the pan parameter already includes a format description and example. The description's phrase 'against a PAN' confirms the parameter's role but does not add new semantic detail beyond the schema. Baseline 3 applies because the schema handles the heavy lifting.

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 the operation: finding all GSTINs registered against a PAN across states. 'Across states' and 'No taxpayer session required' help distinguish this from sibling tools like verify_gstin and session-related tools. The verb 'Find' plus the specific resource (GSTINs by PAN) makes the purpose unambiguous.

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 provides a concrete use case ('discover a business's registrations') and an important condition ('No taxpayer session required'). It does not explicitly name alternatives or state when not to use the tool, but the context cues are strong enough for an agent to select it appropriately.

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