Get GSTR-3B

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

With no annotations supplied, the description carries the burden of behavioral disclosure. It adds one meaningful behavioral precondition (active taxpayer session) but does not disclose side-effect-free/read-only status, failure modes, or what happens if the session is missing. This is adequate but thin.

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 sentences, front-loaded with the core action and object, then the prerequisite. No wasted words.

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 fetch with no output schema, the description gives the core request shape and a prerequisite but leaves the returned detail fields and error/edge behavior unspecified. It is usable but not fully complete.

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%: year and month already have descriptive examples and value constraints. The description adds no parameter-specific meaning beyond 'return period', which is redundant with the schema. 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 names the specific artifact (GSTR-3B monthly summary return) and the action (Fetch details for a return period), clearly distinguishing it from the sibling get_gstr2b by return type. The 'monthly summary' qualifier removes ambiguity about which compliance filing the tool targets.

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?

It provides the prerequisite context 'Requires an active taxpayer session,' which tells the agent this call depends on a prior session step. However, it does not explicitly say when to prefer this over get_gstr2b, track_gst_returns, or other return-listing siblings, so the routing logic is mostly implied by the tool name.

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