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

With no annotations, the description carries the disclosure burden, and it does unusually well: it previews the profile sections and volunteers limitations (unverified or closed venues, overlapping or non-comparable figures, known_gaps and where to go instead). It does not state read-only nature, auth, or rate limits, but for a read-style 'get' tool the data-caveat disclosure is genuinely informative.

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?

Purpose is front-loaded in the first sentence, which is good, but the rest is a long chained narrative ('which national annuals... which venues... which figures...') whose clauses, while informative, are not tightly organized. Roughly 110 words for a one-parameter tool is heavier than it needs to be.

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?

There is no output schema, so the description bears full responsibility for explaining return values, and it does: it enumerates the profile's components (before_you_start, known_gaps, sourced narrative, market-size and player-population figures with their bases). An agent knows what it will receive and what the data does not cover.

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?

Schema coverage is 100% and the single `code` parameter is fully enumerated, so the schema already defines the input; the baseline is 3. The description adds only the count of supported markets (twelve), which the enum already conveys, and adds no syntax or format detail.

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 names a concrete resource — a market profile for one of 12 games markets — and the enum of codes reinforces the scope. It clearly differentiates from siblings by stating only these twelve have profiles while any other code routes to search_sources. The opening 'How to research' is slightly indirect, but the substance is specific.

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 gives an explicit when-to-use (the 12 enumerated market codes) and an explicit alternative for everything else ('for any other market code, search_sources with a market filter is what exists'). That is a named sibling and the precise condition that selects it, leaving nothing to inference.

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