Track returns (taxpayer)

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

With no annotations, the description carries the behavioral burden. It discloses that this is a read/list operation scoped to the authenticated taxpayer and requires an active session. It does not mention behavior when the session is missing or expired, output format, pagination, or error conditions, leaving some behavioral traits implicit.

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 consists of two short sentences with the action and object front-loaded and the session requirement stated compactly. There is no filler, no repetition of the tool name, and every clause adds useful information.

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 simple two-parameter list operation with complete schema coverage, the description provides enough to call the tool correctly: purpose, scope, authentication prerequisite, and parameter formats. It stops short of a 5 because it lacks output-shape information, error-handling details, and explicit distinction from track_gst_returns.

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 already documents both parameters with examples, so schema coverage is 100% and the description does not need to add much. The phrase 'return period' loosely aligns with year/month, but the description adds no syntax or format details beyond what the schema provides, so the baseline score of 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 clearly states a list operation over the authenticated taxpayer's filed/pending returns for a return period, which distinguishes it from search tools like verify_gstin and search_gstin_by_pan. However, it does not explicitly differentiate itself from the similarly named sibling track_gst_returns, so it is clear but not fully differentiated.

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 clear prerequisite—'Requires an active taxpayer session'—and implies the tool is for the currently authenticated taxpayer. It offers no explicit guidance on when to choose this over track_gst_returns or get_gstr3b, and no when-not-to-use scenarios, so usage context is implied rather than fully specified.

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