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

Annotations already declare the write/side-effect profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the safety burden is partly lifted. The description adds value by stating the return ('the document and a link to open and edit it'), though it omits that repeated calls are non-idempotent (duplicates) and says nothing about permissions or workspace scoping.

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?

Three sentences, each earning its place: the trigger first, then the return value, then sibling disambiguation. The enumeration of artifact types is compact and directly aids selection rather than padding.

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 two-parameter creation tool with an output schema and full annotations, this is complete — the output schema carries return structure, annotations carry safety, and the description covers the trigger, the outcome, and the sibling routing. Nothing an agent needs to invoke 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 both `brief` and `title` are already documented, and the description does not add syntax or format guidance beyond what the schema provides. The mention of 'topic, brief, or outline' loosely echoes the schema's own wording. Baseline 3 is appropriate when the schema does 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 (create) and resource (document) within the 'Xenition workspace', and enumerates the concrete artifact types it produces (report, article, letter, brief, essay, plan). It explicitly names the siblings it is not (create_slides, find_forms), so an agent can route without opening 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?

Provides an explicit when-to-use trigger ('when the user asks for a written piece') and two named alternatives with the conditions that select them ('For slides use create_slides; for a fill-in template such as an invoice or resume, use find_forms'). Nothing about the routing decision is left to inference.

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