Plan advance tax installments

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is known. The description adds useful behavioral context: it discloses the output (per-installment amounts and shortfalls against paid-so-far) and the calculation basis (net of TDS).

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 two compact sentences with no waste. The core function and schedule are front-loaded, followed by the reported output.

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 read-only, four-parameter tool with full schema coverage, the description is nearly complete: it explains the calculation basis, installment schedule, and return content. Minor gaps remain around edge cases such as omitted paidSoFar or FY-specific behavior, but nothing critical is missing.

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 schema already documents all four parameters, including paidSoFar ordering and fiscal-year format. The description adds only the net-of-TDS framing and installment percentages, so the baseline of 3 is appropriate.

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 states a specific verb and resource: 'Build the advance tax installment plan'. It also specifies the schedule (Jun/Sep/Dec/Mar at 15/45/75/100%) and the net-of-TDS basis, making it clearly distinguishable from a generic tax computation tool.

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 implied usage by saying the plan is built 'for an estimated tax liability net of TDS', but it does not explicitly say when to use this instead of siblings such as compute_tax or what prerequisites are required. The compute_tax-first guidance appears only inside the schema, not the description.

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