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. It usefully discloses that the tool uses the caller's OpenAny gateway credentials and that charges and authorization are determined by the gateway, and it warns that the wikibase_item field appears only when the article has a linked item. It does not explicitly state read-only safety or rate-limit behavior, which keeps it below a 5.

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 definition is three sentences and front-loads the core action immediately. Each sentence earns its place by stating the purpose, the return-value caveat, and the billing/authorization context.

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 seven-parameter lookup with no output schema and no annotations, the description covers purpose, gateway auth/billing, and the key return-value condition. It leaves some edge cases unstated, such as behavior for missing titles or how redirects affect resolution, but the core call requirements are clear.

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 100%, so the schema already documents all seven parameters. The description adds only the mapping of 'English Wikipedia article title' to the titles field and does not explain the fixed enum values or redirects behavior beyond what the schema provides. Baseline 3 is appropriate.

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 uses a specific verb and resource: 'Resolve an English Wikipedia article to its linked Wikidata item ID.' It distinguishes this from sibling tools such as wikimedia_get_wikidata_entity and wikimedia_get_wikidata_entity_search by framing the action as resolving an article title into a linked Wikidata ID.

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 verb 'Resolve' implies the tool is used when you have an English Wikipedia article title and need its Wikidata item ID. However, the description does not explicitly say when to use this versus wikimedia_get_wikidata_entity, wikimedia_get_wikidata_entity_search, or other wikimedia lookup tools, and gives no when-not guidance.

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