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

Annotations already state readOnlyHint=false and destructiveHint=false, and the description adds the key behavioral facts that go beyond them: a new item is created, the new item is returned, and the original is left unchanged. It does not cover idempotency or failure behavior, but the non-destructive outcome is explicitly disclosed.

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, zero filler: the trigger condition is front-loaded, followed by the concrete format list and examples, then the side-effect note. 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?

For a conversion tool with full schema coverage, annotations, and an output schema, the description supplies what structured data cannot: the use trigger, the example mappings, and the create-new/leave-original-intact outcome. Nothing an agent needs 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 coverage is 100%, so all three parameters (artifactId, target, title) are already documented in the schema, including the target vocabulary. The description restates the target options and the source-item concept but adds no format details, defaults, or constraints beyond the schema, making baseline 3 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?

The description names a specific verb (turn/convert) and resource (a Xenition item into another format) and enumerates the concrete outputs: board, calendar, form, slides. It is clearly distinguishable from creation siblings like create_board or create_slides because it operates on an existing source item.

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?

It gives an explicit trigger: 'Use this when the user wants one of their Xenition items turned into a different format,' reinforced by two conversion examples. It stops short of naming when-not or pointing to an alternative tool, so it is clear context rather than full routing guidance.

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