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: not whether the call is read-only or mutating, whether it requires auth, rate limits, or what it returns. 'LIVE' hints at a real-time backend but is not actionable.

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 a single short sentence, but its brevity reflects under-specification rather than efficient information density. The only content is provenance, which does not earn its place as the sole statement about the tool.

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 with no annotations, no output schema, and an empty input schema, the description should explain the purpose, expected inputs, and result shape. It supplies none of that, leaving the agent unable to determine what the tool does or how to call it meaningfully.

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 declares zero parameters (additionalProperties: true), so there is no parameter semantics to document and no coverage gap to compensate for. Baseline 4 applies when there are no params.

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 merely restates the tool name ('qloo_audience_demographics') and adds provenance metadata ('proxied from this server's `qloo mcp` (LIVE)'). It never says what the tool actually does, what an 'audience demographics' operation returns, or how it differs from siblings like qloo_compare_audiences or qloo_where_popular.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives. The one descriptive clause concerns deployment ('LIVE'), not invocation context, so an agent has nothing to route on.

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