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

Annotations already declare readOnly/idempotent/closed-world; the description adds real context beyond them: the six result buckets, a separate checker that re-derives totals, a signed receipt from Nityaflow, and in-memory processing with no storage. It also rules out any write-back to the GST portal, which is the key behavioral fear for this domain.

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?

Front-loaded with the one-line purpose followed immediately by the input sources and the result categories; almost every clause carries information. The middle sentence listing six buckets is dense but hard to trim without losing classification semantics.

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?

No output schema exists, so the description compensates by enumerating the exact outcome categories and noting the totals re-check and receipt. Combined with the privacy and no-filing statements, an agent has everything needed to call it correctly and set expectations for the result.

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%, so the baseline is 3, but the description adds meaning the schema lacks: 'books' can come from named accounting packages or any list, and the reconciliation semantics of gstr2b vs books are spelled out. It does not add anything about tolerance or period beyond the schema.

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 and resource ('Matches the supplier invoices in GSTR-2B against the purchase register') and frames the domain ('India GST input tax credit check'). None of the siblings (agent_payment_check, create_workflow_draft, get_workflow_guide, verify_receipt) could be confused with it.

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?

Gives clear context for use: reconciliation of portal data against books from Tally, Zoho Books, Busy, QuickBooks or any list, plus a boundary ('never files or accepts anything on the GST portal'). It does not explicitly route the agent to or away from siblings such as verify_receipt, so no explicit alternatives are named.

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