calculate_uk_council_tax

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

Discloses output ('Returns annual and monthly council tax') and implies no side effects. As a calculator, this is transparent; no annotations needed.

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 concise sentences plus a pointer to related tools. No wasted words, front-loaded with purpose.

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?

Covers basic inputs and outputs, but misses details like default region (England) and how band and region combine to compute tax. With an output schema, this is adequate but not thorough.

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?

Description refers to 'local authority' instead of the schema parameter 'region', causing semantic mismatch. While schema covers 100%, the description adds confusion rather than clarity.

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?

Clearly states 'Compute UK Council Tax' with specific parameters (band and local authority). Distinguishes from other tax calculators like calculate_uk_income_tax by targeting a specific tax type.

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?

Provides context 'Use for UK residents and home buyers' and references list_bundles for related calculators. Lacks explicit when-not-to-use or alternatives, but the context is sufficient.

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