lookup_council_tax

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

With no annotations provided, the description fully discloses that the tool does not perform an actual API call but returns a fixed 'coming soon' response, and explains the reason (avoiding credit consumption on an unavailable endpoint). This is transparent about the tool's current behavior.

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 consists of two short sentences: the first clearly states the purpose, and the second explains the current non-functional behavior. Every sentence adds value with no redundancy.

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?

For a simple tool with one parameter and no real functionality, the description is complete. It explains what the tool does, its current state, and the behavior. An output schema exists, so return values do not need further explanation.

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 single parameter 'uprn' is described in the schema as 'Unique Property Reference Number' with 100% coverage. The description does not add additional meaning beyond what the schema provides, meeting the baseline but not exceeding it.

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 the verb 'Get' and the resource 'VOA council tax band (A-H) and billing authority for a UPRN'. It explicitly mentions the output (band and authority) and the required input (UPRN). This distinguishes it from sibling tools like 'lookup_epc' or 'lookup_property'.

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 notes that the tool is 'in development and not yet production-ready' and returns a 'coming soon' response without hitting the API, informing agents that it is safe to call but does not provide real data. However, it does not explicitly mention when to use it versus alternatives or provide exclusions.

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