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

Annotations already declare a safe, closed-world read. The description adds real value by disclosing the exact payload: currency (DKK), VAT basis (excl. VAT), and the presence of sub-services, so the agent knows the shape of the result without an output schema.

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?

A single front-loaded sentence with zero filler; the parenthetical category list and field enumeration both earn their place. Slightly dense with two stacked lists, but no wasted prose.

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?

With no input schema, no output schema, and minimal annotations, the description carries the return-value burden and does so well by naming every returned field. Only gap is not clarifying the relationship between 'starting price' here and the sibling get_prices.

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 tool takes no parameters, so there is nothing for the description to disambiguate; the baseline applies. The description correctly notes the result covers all service categories without any filtering input.

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?

States a specific verb and resource ('List Adbull's services') and enumerates the service categories and returned fields (short description, page URL, starting price in DKK excl. VAT, sub-services). It does not explicitly differentiate itself from the sibling get_prices, even though pricing appears in both.

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?

Usage is implied: call it to get an overview of what Adbull offers. There is no explicit when-to-use or when-not, and no routing to alternatives such as get_prices for deeper pricing questions, despite the overlap.

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