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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: the response carries has_staged_changes/staged_locales/staged_updated_at, and that a 404 conflates unknown-id with wrong-help-center, which materially changes how an agent should interpret a failure. It does not cover rate limits or pagination (not applicable here).

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 purpose then usage, followed by Returns and Errors sections that earn their space. The explicit 'Args' block largely duplicates the schema and could be trimmed, and 'Read-only.' is redundant with readOnlyHint=true, but overall it is well-organized and readable.

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?

With no output schema, the description carries the return-value burden and does so concretely (full article with per-language title/content/slug, categories, external_id, staged-changes flags) plus error semantics. For a read tool with a well-documented schema, nothing needed 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 description coverage is 100%, so all three parameters are already documented, including the response_format enum semantics and the agent_key credential handling. The description's 'Args' section mostly restates that. Baseline 3 applies because the schema is doing the heavy lifting.

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 (read) and resource (one article by id) in the first sentence, and explicitly contrasts with the two nearest siblings (helpcenter_list_articles, and implicitly search_articles via the 'after a search' reference). An agent can route correctly without opening the schema.

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?

Gives an explicit when-to-use condition ('already know the id — after a search, or before editing'), names the alternative it replaces ('instead of paging through helpcenter_list_articles'), and adds a second, non-obvious use case: checking has_staged_changes before a live update to avoid colliding with staged edits.

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