timps_gst_compliance

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

With no annotations, the description must disclose behavioral aspects, but it only states 'Generate...' without revealing side effects (e.g., file creation, API calls), output format, or required credentials. The tool likely performs mutations, but nothing is disclosed, making it risky for an agent to invoke.

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 is a single, compact sentence with no redundant text. Every word adds value, listing specific outputs and geographic scope. It is front-loaded and easy to parse.

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 tool with two well-described parameters and no output schema, the description covers the basic functionality. However, as a compliance tool it lacks context about expected input format, typical use cases, or any caveats (e.g., data requirements). It is minimally complete but not robust.

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?

Both parameters are already described in the schema (request: Plain-English task/context; language: default python). The description adds no additional meaning beyond that, so the schema carries the burden. Baseline of 3 applies due to 100% schema coverage.

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 tool's purpose: generating GST-specific outputs (GSTR-1/3B filings, e-invoice XML, ITC reconciliation reports) and scopes it to India GST. This distinguishes it from sibling compliance agents (e.g., timps_fssai_compliance_agent, timps_dpdp_act_auditor).

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?

No guidance is provided on when to use this tool versus alternatives. The description only lists what it generates, without specifying typical scenarios or exclusions. There is no mention of prerequisites or when it would be inappropriate, leaving the agent to infer usage.

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