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

The description adds meaningful behavioral details beyond the annotations: it clarifies that the API returns no total count, pagination is offset-based, and no result ceiling indicator exists. The annotations already indicate read-only/open-world behavior, so the description only needs to add quirks and return format, which it does.

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?

Three tight sentences: the first states exactly what the tool does, the second gives return-type guidance, and the third addresses pagination can. There is no filler or redundant restating, and the most important details are front-loaded.

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?

Combined with the fully-covered input schema, attached output schema, and read-only/open-world annotations, the description is complete for an agent to invoke the tool correctly. It also covers important behavioral caveats (pagination without total count) that the schema would not.

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 covers 100% of parameter semantics, so the baseline is 3. The description adds only marginal color — e.g., plain-language examples for type values — but the formal parameter documentation already contains the same meaning for query, limit, offset, and language.

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 opens with a specific verb and resource ('Search Wikidata for items or properties by text query') and explicitly states the result type ('QIDs or PIDs with labels, descriptions, and match metadata'). This clearly distinguishes the tool from direct-lookup siblings like wikidata_get_entity, which fetch by exact ID rather than full-text search.

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 gives clear contextual guidance on when to set type="item" vs type="property", and warns about pagination. It doesn't explicitly state 'use wikidata_get_entity for direct lookups' or list exclusions, but the search semantics are implied well enough that an agent can select this tool when the user has a text query.

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