Plan advance tax installments

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

Annotations declare readOnlyHint=true, consistent with description of planning/reporting. Description adds behavioral details: the installment schedule, percentages, and shortfall reporting. No contradictions.

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?

Two sentences, front-loaded with key purpose and output details. Every sentence is meaningful with no fluff. Very efficient.

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 4-parameter tool with no output schema, description covers what the tool does and what it returns (per-installment amounts and shortfalls). Missing error conditions or assumptions, but sufficient for standard use.

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 baseline 3. Description adds minimal parameter info beyond schema (e.g., 'net of TDS' linking estimatedTax and tdsExpected), but doesn't elaborate on each parameter. Adequate but not exceptional.

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?

Description clearly states the tool builds an advance tax installment plan with specific due dates (Jun 15, Sep 15, Dec 15, Mar 15) and percentages (15/45/75/100%). It reports per-installment amounts and shortfalls, distinguishing it from siblings like compute_tax or list_deductions.

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?

Description implies use when you have an estimated tax liability net of TDS and want to plan installments. However, it does not explicitly state when not to use it or mention alternatives like compute_tax, though the input schema hints at using compute_tax first. Still clear enough for most use cases.

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