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

No annotations are provided, so the description carries the burden. It mentions using 'latest IRS brackets from CDN data', indicating up-to-date rates and a data source, which is useful. However, it does not disclose what happens to state tax input (ignored or used for state-level calc) or potential limitations like dependency on CDN availability.

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?

Single sentence, front-loaded with the core purpose, including key details (15.3%, QBI, quarterly payments) and data source. No wasted words.

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?

Given the tool is a calculation tool, the description covers the essential purpose and inputs. No output schema is provided, but the description mentions what is calculated (tax, QBI, quarterly payments) which indicates outputs. It lacks detail on how state tax might affect output, but the core functionality is adequately specified for a calculator tool.

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 parameters are fully described. The description adds context that netEarnings is the primary input for the core calculation, and hints that state and filingStatus may factor into the calculation but does not specify how. This adds value beyond the schema by implying the role of these parameters in the broader tax calculation.

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?

Clear verb 'Calculate', specific resource 'US self-employment tax', and distinct aspects (QBI deduction, quarterly payments). Differentiates from siblings like calculate_freelancer_tax and calculate_quarterly_tax by specifying self-employment tax specifics and use of IRS brackets.

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 use for self-employment tax calculations, but does not explicitly state when to use it over alternatives like calculate_freelancer_tax or calculate_quarterly_tax. No exclusions or alternative recommendations are given.

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