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

Discloses substantial behavior beyond the annotations: default archiving after publish, per-call confirmation with an opt-out, the Admin/publishing permission requirement, and that failed items return the publishing error. None of this is implied by readOnlyHint=false / openWorldHint=true, so it genuinely adds value.

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, but the confirmation instruction is stated twice ('you confirm each call' and 'confirm with the user before each call'), and the permission/auth sentences are somewhat scattered. Thematically useful but not tight.

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 mutation tool with no output schema, the description covers permissions, destructive-adjacent behavior (archiving), error returns, confirmation policy, and credential requirements—everything an agent needs to invoke it safely and correctly.

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%, and the schema already documents item_ids, publish_as (Xero only), and publish_to. The description adds no syntax or format detail beyond the schema, so the baseline 3 for fully-covered parameters applies.

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 (publish) and resource (Ready items) with explicit scope: sending extracted data and document image to the connected accounting software. This clearly distinguishes it from dext_archive_items, dext_export_items, and dext_update_item in the sibling set.

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?

Explains the eligibility condition clearly ('Only Ready items publish; others come back with the missing field'), which routes the agent on when candidates are valid. It doesn't explicitly name a sibling alternative or a when-not scenario beyond the Ready gate, so it stops short of a 5.

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