save_gstr1_data

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

With no annotations, the description carries the behavioral disclosure burden. It reveals the asynchronous polling pattern, the need to wait for COMPLETED status, and the return shape with reference_id. It could add more about failure modes or retry behavior, but it is substantially transparent.

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?

Purpose is front-loaded, followed by the critical polling instruction, then concise parameter definitions and return summary. Each sentence contributes necessary information without filler or repetition.

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?

The description covers workflow order, parameter semantics, and the asynchronous return contract, which is sufficient for correct invocation. Minor gaps remain around detailed error scenarios and explicit prerequisites beyond the token, but the provided output schema and sibling context reduce that burden.

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 0%, so the description must compensate, and it does. Every parameter is explained: access_token source, gstin format, ret_period format with example, and gstr1_data payload structure including key sections like b2b, b2cl, b2cs, hsn, and docs.

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 ('Upload'), resource ('GSTR-1 data'), destination ('GST portal'), and purpose ('for validation'), plus workflow position ('Step 2'). This clearly distinguishes it from sibling tools like file_gstr1 and get_gstr1_summary.

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?

Provides explicit next-step guidance: call check_return_status with the returned reference_id and poll until COMPLETED before proceeding. It does not explicitly name negative alternatives or when not to use this tool, but the workflow step and sequencing make usage clear.

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