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

Annotations already establish a non-destructive write (readOnlyHint=false, destructiveHint=false). The description adds real value on top: it creates a NEW item, returns it, and explicitly leaves the original unchanged. It omits idempotency behavior (repeated calls would produce multiple new items, consistent with idempotentHint=false), which is the only notable gap.

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?

Two sentences, front-loaded with the usage trigger, then examples, then the key behavioral fact. No filler; every clause earns its place.

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 an output schema present and full schema coverage, the description needn't document return values. It covers when to use it, what it produces, and that the source is untouched. Only minor gaps remain (no failure/unsupported-target behavior), so it is close to complete for a moderate-complexity tool.

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 artifactId, target, and title. The description restates the target options in prose ('board, calendar events, a form or a slide deck') but adds no syntax or defaults beyond what the schema provides. Baseline 3 is appropriate when the schema carries the parameter burden.

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 (turn into another format) and resource (a Xenition item/artifact), and lists the concrete target formats. The 'repurpose an existing item' framing implicitly separates it from siblings like create_board or create_slides that build from scratch, and the meeting-notes-to-board example makes the transformation unambiguous.

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?

Opens with an explicit trigger: 'Use this when the user wants one of their Xenition items turned into a different format,' followed by representative examples. It gives clear positive context but names no alternatives or when-not conditions (e.g. use create_board to start a fresh board), so it stops short of full routing guidance.

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