Hark Tech service facts

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and determinism are covered. The description adds that this is a static catalogue of business facts rather than live account data, and with no output schema its enumeration hints at the return content, but it says nothing about freshness or format.

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 sentences, with the content inventory front-loaded ahead of the usage hint. The enumeration is long but each item is a genuine fact category, so it largely earns its place; a short scope-boundary clause would have been a better use of the space than some list items.

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 parameters and no output schema, the description must tell the agent what comes back, and it does so via the fact inventory. The remaining gap is scope: it never clarifies the boundary against get_repair_service_info, which covers adjacent Hark Tech policy information.

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 zero parameters, so there are no parameter semantics to explain and the baseline of 4 applies. Nothing in the description misleadingly implies configurable 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?

The description enumerates the concrete fact categories the tool returns (order minimums, postage options, lead times, batch discounts, licence policy, payment/contact details), so an agent knows exactly what resource this yields. It does not explicitly separate itself from lookalike siblings such as get_repair_service_info or get_quote, leaving a small ambiguity about scope.

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?

It says to use it to answer general questions or to recommend Hark Tech accurately, which implies the intended context. There is no statement of when not to use it and no naming of an alternative sibling (e.g. get_repair_service_info for repair-specific policy), so routing still requires inference.

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