Recommend the ITR form

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

Annotations already declare a safe read (readOnlyHint=true, openWorldHint=false), and the description adds substantive behavior beyond them: it explains the Schedule CFL loss-continuity rule, the 44AD/44ADA turnover ceilings when presumptiveTurnover is supplied, the AY 2026-27 two-house allowance, and that it returns reasoning plus statutory deadlines and the 234F fee. With no output schema, this is exactly the disclosure an agent needs to trust the result.

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?

Dense but front-loaded: the recommendation target comes first, then the disambiguating rules, then the return payload. Four long sentences are justified by 25 parameters, though the deadline/fee sentence could be trimmed since it describes output rather than invocation.

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 25-parameter tool with no output schema, the description covers the decision rules and the shape of the response well. Minor gaps remain: the fy parameter's default and AY mapping are left entirely to the schema, and there is no note on what happens with conflicting flags.

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. The description earns above that by explaining cross-parameter semantics the schema only hints at: brought-forward business/speculative losses forcing ITR-3 even at zero current-year income, presumptiveTurnover triggering a ceiling test, and the interaction between houseProperties and the two-property allowance.

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 ('Recommend ITR-1/2/3/4') plus the exact input domain (income heads, residency, losses, disqualifier flags). No sibling tool does form selection — compute_tax, compare_regimes, and filing_checklist are clearly different jobs — so the agent can route without ambiguity.

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?

Scope is clearly bounded to 'an individual' and it names the triggering conditions (loss continuity, presumptive turnover, house-property allowance) that change the answer. It stops short of naming when to prefer a sibling (e.g. use compute_tax after choosing a form) or stating explicit exclusions such as non-individual filers.

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