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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: no read/write nature, no auth requirements, no rate limits, no return shape, no cost. The provenance sentence conveys deployment mechanics, not behavior an agent can act on.

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?

It is short, but the single sentence is spent on name repetition and proxy provenance rather than front-loading purpose. Brevity achieved by omission rather than by editing, so it does not earn its place.

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 tool sitting in a 21-sibling qloo/knos namespace with no annotations and no output schema, the description supplies no distinguishing information at all. An agent cannot determine what this tool returns or when it is the right choice.

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 schema declares zero parameters, so there is no parameter semantics for the description to explain; the baseline for a zero-param tool is 4. The description neither misleads nor adds anything here.

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 only restates the tool name and asserts provenance ('The official qloo-harness tool qloo_recommend, proxied from this server's `qloo mcp`'). It never states what the tool does — no verb, no resource, no output kind. Among siblings like qloo_rank, qloo_compare_audiences, and qloo_trends, an agent has no basis to select this one.

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?

No when-to-use, when-not-to-use, or alternative routing is given. The '(LIVE)' marker hints at data freshness but does not explain what condition should select this tool over qloo_rank or qloo_find_tags.

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