calculate_us_property_tax

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

With no annotations provided, the description carries the burden. It discloses the tool as an estimate and specifies the return fields (home_value, effective_rate_pct, annual_property_tax, monthly_property_tax), giving the agent a clear expectation of output. It does not elaborate on data source or accuracy, but for a calculator this is sufficient.

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 only two sentences, front-loaded with the core purpose and return format, followed by a pointer to related tools. Every sentence earns its place with no excess verbiage.

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's low complexity and the presence of an output schema (though not detailed), the description adequately covers the purpose and returns but omits the list of supported states (only 6 in enum vs 'by state' implying all US states). Some nuance is missing, but overall it is sufficient for basic understanding.

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?

The input schema already covers both parameters with descriptions (home_value: 'Assessed home value in USD', state: 'State (affects effective property tax rate)'), so the description adds minimal additional meaning. The mention of 'effective tax rates' provides context but does not enhance parameter understanding 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 clearly states 'Estimate annual US property tax by state using effective tax rates,' specifying the verb (estimate), resource (US property tax), and scope (by state). It distinguishes itself from sibling calculators like French property tax tools through explicit mention of US and state.

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 provides context by referencing a bundle for related calculators ('See list_bundles for related 'finance-us' calculators'), but does not explicitly state when to use this tool versus alternatives, nor does it include exclusions or prerequisites beyond what the schema implies.

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