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

With no annotations, the description itself discloses that the result is an 'estimate' and that it relies on 'latest CDN data,' which suggests current tax information but remains vague. It does not disclose assumptions, state-versus-federal scope, or how the mentioned components surface in the output, leaving the agent to infer behavior.

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?

Three very short sentences front-load the purpose and supporting context. Every phrase adds information, although 'CDN' is an unexplained acronym; on structure alone it is exemplarily concise.

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?

The description captures purpose, scope, components, and data freshness, but with no output schema and no annotations it leaves unstated what exactly is returned and whether state income tax is included despite the state parameter. For a 5-parameter calculator this is adequate but not completely self-contained.

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 the baseline is 3 and the description need not repeat parameter docs. The phrase '1099-K income' and 'reselling, gig work' adds contextual meaning to grossReceipts and expenses, but it does not clarify options like state or costOfGoodsSold 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?

The description names a specific verb ('Estimate'), a specific income type ('1099-K income'), and an example context ('reselling, gig work'). It also lists components (SE tax, QBI, quarterly 1040-ES) that differentiate it from generic tax calculators among the siblings.

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 implies the use case—1099-K income from reselling or gig work—but it never states when not to use it or names alternatives such as calculate_se_tax or calculate_freelancer_tax. Given the large sibling set of tax calculators, the omission is noticeable, though the 1099-K qualifier gives some guidance.

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