Wikidata Alignment Search

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds that each result names the join key used for entity resolution, which is useful beyond the annotations, but it says nothing about pagination behavior despite limit/offset parameters.

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 space is partly spent on internal references that mean nothing to an agent: the :data:`world_reference_mcp.api.wikidata.ENTITY_TYPES` symbol path and the internal code 'EH-032'. The core statement should be front-loaded in plain language instead.

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?

An output schema exists, so return values need not be described. Still, for a 3-parameter search tool the description does not clarify what a result actually contains, how the external-id match is performed, or how to page through results, leaving real gaps for invocation.

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?

With 0% schema description coverage the description must carry parameter meaning, and it does document the required entity_type with four concrete values that the schema does not enumerate. However, limit and offset are entirely undocumented, including their defaults and any maximum, so compensation is only partial.

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?

It names a concrete verb and resource ('List Wikidata items'), but the scope statement 'carrying the external id ``entity_type`` matches on' is convoluted and leaves it unclear whether the search returns Wikidata items, external-id values, or both. The enum values help an agent reason about the domain, but there is no differentiation from the other search siblings.

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 never states when to choose this tool over taxonomy_ncbi_search, taxonomy_gbif_search, or the other siblings, nor any when-not conditions. The enumerated entity_type values hint at applicability but are not usage guidance.

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