vat_guide

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

With no annotations, the description carries the full burden of explaining behavior. It only says 'guidance' and 'DEMO', neither of which clarifies what the tool actually does, how it responds, or what limitations exist. The 'DEMO' label hints at incompleteness but is not elaborated.

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 very short and front-loaded with the topic, which is positive. However, it is under-specified and includes the ambiguous 'DEMO' tag. It is concise but at the expense of essential operational detail.

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?

Despite having only one parameter and an output schema, the description provides minimal operational context. An agent cannot infer how to formulate a query or what response to expect. The 'DEMO' label creates additional uncertainty, and no details about the output schema are given.

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 has one required parameter 'query' with no description, and the tool description does not mention it at all. With 0% schema description coverage, the agent has no clue what to put in the query, how to format it, or what kinds of questions are valid.

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 tool provides guidance on Kenya VAT registration, rates, and filing. While it lacks a strong verb, the noun 'guidance' makes the purpose clear. It is also distinguishable from sibling tools that cover PAYE, PIN, tax calendar, withholding, and incentives.

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 gives no advice on when to use this tool versus alternatives. It does not mention that it is for VAT-specific queries or exclude other tax topics. No explicit when-to-use or when-not-to-use guidance is provided.

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