calculate_uk_council_tax

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

No annotations are provided, so the description must fully disclose behavior. It states it computes council tax but does not clarify if it fetches rates or is purely formulaic. It also does not indicate lack of side effects, authentication needs, or data freshness. The mention of 'local authority rate' implies a dependency not reflected in the schema, reducing transparency.

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?

Description is short (two sentences) and front-loaded with purpose. Each sentence serves a role: purpose, usage, and referral to related tools. No redundant words. However, the mismatch with schema slightly undermines conciseness by introducing an inaccurate term.

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 presence of an output schema, the description need not detail return values. However, it fails to mention that only England, Scotland, Wales are supported (no Northern Ireland), and the input/output mapping is incomplete. The reference to 'local authority' is unsupported, leaving gaps in understanding the tool's scope.

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% with parameter descriptions, but the description introduces 'local authority rate' which does not match the 'region' parameter in the schema. This mismatch could confuse the AI. It does not add value beyond the schema except for stating output (annual and monthly council tax).

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 verb 'Compute' and resource 'UK Council Tax' with inputs band and local authority. Differentiates from siblings by mentioning UK-specific context and referencing related 'finance-uk' calculators. However, the phrase 'local authority rate' is ambiguous as the schema only has 'region', causing minor confusion.

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 target users ('UK residents and home buyers') and directs to list_bundles for related calculators, giving some usage context. But lacks explicit when-not-to-use or alternatives, and the reference to 'local authority rate' may mislead about which specific parameter to use.

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