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

Annotations already declare destructive=true and idempotent=false, and the description adds substantial context on top: no review step, ongoing sync of title/subtitle/description/image/handles, audited, and the specific 409 qid_merged refusal with a redirect to wikidata_item. That is exactly the beyond-annotation behavioral detail this dimension rewards.

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?

Front-loaded with the core action and structured as operation → behavior/refusals → alternative. Dense and long in absolute terms, but nearly every clause (sync, refusals, 409 code, audit, dry run) carries operational weight, so little is wasted.

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 explained, and the description fills the remaining gaps: creation path, sync behavior, refusal/error handling, audit trail, dry-run default, and the sibling alternative. Nothing an agent needs to call it correctly is missing.

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 both params are documented in-schema, so the baseline is 3. The description adds meaning beyond the schema, though: it clarifies that dry_run (the default) 'names the entries already on the item,' and explains the QID's merged-away handling that the schema only constrains by regex.

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?

States a specific verb+resource ('Create a live entry straight from a Wikidata item') and frames it as the Console → Create from QID flow, so the agent knows exactly what operation is performed. It also distinguishes itself from the sibling propose_new_entry by contrasting 'no review step' with 'propose it for review instead.'

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?

Explicitly names the alternative ('To propose it for review instead, use propose_new_entry with qid') with the condition that selects it. It also documents refusal conditions (already on the item, or on a merged item) and routes the agent to the surviving QID via wikidata_item, which is genuine when/when-not guidance.

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