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

Goes well beyond the annotations: it explains that re-sending identical title/content/tags is a no-op with status "unchanged" (sharpening idempotentHint into concrete semantics), that overlapping content is refused with a named conflict, that changes are live for the AI assistant immediately, that creation is attributed to this AI connection, and that nothing is sent to anyone. These are exactly the mutation consequences an agent needs before writing.

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 and scoping before the behavioural details, and nearly every sentence carries information. It is dense to the point of being cramped, stacking parenthetical asides and status tokens ("unchanged", "conflict") in a single block, which slightly hurts scannability.

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 nonetheless surfaces the two meaningful outcomes (unchanged no-op and named conflict). For a two-required-parameter upsert with an idempotency requirement, nothing an agent needs in order 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 the schema already documents all four parameters including tags format, length limits and source_id's role. The description only adds the nuance that source_id targets *manual* articles, which is a small but real increment over the schema wording. 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?

States a specific verb pair and resource — 'Create a new article ... or update an existing manual article by source_id' — and immediately rules out the confusable neighbour ('not Spun's product documentation; use search_knowledge for that'). An agent can distinguish this from kb_get_article, kb_list_articles and search_knowledge without reading any 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 explicit routing rules: use search_knowledge for product documentation instead, omit source_id to create, supply source_id to update, and on a conflict 'update that article by source_id or change the text'. When-to-use, when-not-to-use and the fallback path under rejection are all present.

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