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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered, yet the description adds genuine behavioral context: CC0 licensing, zero point cost, and the notable failure mode where supplying fields returns privacy_consent_required until the controller accepts the current privacy version, with an explicit warning not to fabricate acceptance. The one confusing element is 'If you supply fields,' since the schema exposes only a single 'search' parameter, so the trigger condition for that error is not fully pinned down.

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?

The text is short and front-loaded, leading with the core verb-and-resource statement before caveats, and nearly every clause carries usable information (CC0, no points, no URL, privacy consent). The closing 'Do not invent that acceptance' is somewhat redundant with the preceding sentence, and the telegraphic sentence fragments make the privacy condition harder to parse than necessary.

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 single-parameter, read-only lookup with no output schema, the definition covers what an agent needs to call it: input form, licensing, cost, disambiguation from Wikipedia, and a blocking consent gotcha. It does not describe what the response contains (a bare entity id versus a richer object) or behavior when nothing matches, which is the main remaining gap.

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 description coverage is 0%, so the description must carry the burden, and it does meaningfully narrow the input: it takes a short name rather than a URL, which is exactly the ambiguity an agent would otherwise hit with a generic 'search' string field. It still does not state matching or ambiguity behavior (e.g., what happens with multiple matches) or restate the 1-60 character bound, leaving some semantic gap.

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 first sentence names a specific verb (find) and a specific resource (one Wikidata entity id) plus the input form (a short name). It also explicitly distinguishes itself from the closest sibling, hub_wikipedia, with 'This is not a Wikipedia article,' so an agent can route correctly without opening either schema.

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?

The description states clear boundaries of use: it does not accept a URL, does not spend points, and is not for Wikipedia articles, which implicitly routes URL lookups and article lookups elsewhere. It stops short of naming the intended alternative tool by name (e.g., hub_wikipedia or a URL-based hub), so the when-to-use-this-instead signal is inferential rather than explicit.

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