get_tax_summaryGST snapshot for a period: taxable value, CGST/SGST/IGST/cess, total tax and invoice count (B2B + B2C split), plus TCS and TDS collected per channel. India GST.
| Name | Required | Description | Default |
|---|---|---|---|
| period | No | Reporting period: mtd (default), last-month, qtd, or ytd. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe/read-only nature is covered. The description adds that the tool returns an aggregated snapshot with invoice count splits and TCS/TDS per channel, which provides some behavioral context beyond the schema, but it does not disclose details like default period handling or data-source caveats.
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?
One compact sentence delivers the tool's purpose, scope, and key output fields, ending with 'India GST' for regional context. No filler or repetition of schema details.
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?
With a simple optional parameter, full schema coverage, a read-only annotation, and an existing output schema, the description provides enough context for an agent to understand what the tool does and when to invoke it. The inclusion of B2B/B2C split and channel-level TCS/TDS adds useful completeness.
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 single 'period' parameter is fully documented in the schema with an enum and default value, and the description's phrase 'for a period' aligns with it but adds no new semantic detail beyond the schema. Baseline 3 is appropriate given the 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 specifies a GST tax summary for a period, enumerating the exact components returned (taxable value, CGST/SGST/IGST/cess, TCS, TDS). It is distinct from sibling tools like get_state_wise_tax or get_gstr1_summary by focusing on a period-based aggregate snapshot, though it does not explicitly name those alternatives.
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 clear context: use this for a period-level GST snapshot in India, with a defined list of included figures. It does not explicitly state when not to use it or name alternative tools, but the scope is specific enough to indicate its intended use case.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct data points (e.g., get_analytics_summary vs get_brand_score). However, 'search' and 'search_catalog' have overlapping functionality and could cause confusion, and 'fetch' is a helper tied to 'search', adding minor ambiguity.
The majority use consistent verb_noun snake_case (e.g., get_inventory, list_stores). Exceptions like 'fetch' and 'search' (without object) break the pattern, but they are few.
43 tools is excessive for a data-retrieval-only API. Many get_* and search_* tools could be consolidated (e.g., search_catalog, search_inventory, search_orders are similar). The large number will overwhelm an agent.
The tool set is entirely read-only (get, search, list, fetch). There are no create, update, or delete tools, which is a critical gap for managing e-commerce operations. Agents can only view data, not act on it.