GST, TDS, ROC and payroll due dates

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

Annotations already establish read-only, idempotent, closed-world behavior, yet the description adds genuinely new context: dates are standard statutory dates, government extensions are excluded, and each entry comes with legal basis and official authority. That tells the agent how much to trust the output before it calls. It does not discuss output ordering or completeness limits, so it is not exhaustive.

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?

Four sentences, front-loaded with purpose, followed by defaults, parameter nuance, and the accuracy caveat. The defaults and state sentences overlap with what the schema already states, so some content is duplicated rather than wasted.

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?

There is no output schema, and the description compensates by stating what each date carries (legal basis, official authority) and, crucially, the limitation that extension dates are missing. For a four-parameter, zero-required read-only lookup this is close to complete; a hint on the shape or count of returned entries would close the remaining gap.

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 100%, so all four parameters are already documented, including that `state` drives the QRMP GSTR-3B date and that `from`/`to` default to today in IST and 30 days later. The description restates those defaults rather than adding new meaning, so baseline 3 applies.

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 opens with a specific verb and resource ("Lists standard Indian compliance due dates"), enumerates the covered categories (GST, TDS, advance tax, EPF/ESI, ROC), and scopes the result to a date range. It is unmistakably distinct from the sibling tools, which are all single-value validators or holiday/pincode lookups.

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 gives clear operating context: defaults to the next 31 days in IST, pass a state only when QRMP GSTR-3B applies, and a warning that extensions are excluded so dates must be confirmed against the official notification. It stops short of naming alternatives (e.g. pointing to india_holidays for public holidays or state_info for registration details), which keeps it from a 5.

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