taxcredit-engine__calculate_tax_credit

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

With no annotations, description discloses key behavioral traits: auditable calculation, indeterminate result for missing facts, and disclaimer that it's not tax advice. Covers essential behavioral aspects for a calculation tool.

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 clear, front-loaded sentences. The bracketed prefix provides context without extra fluff. Every sentence adds value, with no waste.

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?

Coverage is adequate for invoking the tool: it explains what to provide and what to expect. However, it does not describe the return value structure or mention whether it is read-only (likely, but not stated). Lacks details about output format.

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 0%, but description adds meaning by specifying credit must be one of the listed types and facts must contain explicit eligibility facts. This significantly clarifies parameter usage beyond the bare 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?

Description clearly states it calculates an auditable tax-credit scenario for specific credits (45Q/45V/45Y/48E/45X). Differentiates from sibling tools like 'get_rule_pack' and 'verify_tax_credit_result' by being the main calculation entry point.

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?

Explicitly requires facts to contain credit-specific eligibility facts, and warns that missing facts return indeterminate. Provides clear context for use, but does not explicitly mention alternatives or when not to use.

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