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

Annotations (readOnlyHint=false, destructiveHint=false) are consistent with the description, which discloses detailed behavior: conversion types, child re-assignment, element stays on board, link via get_whiteboard, one-time conversion, title defaulting, and workspace requirement. This goes well beyond annotations and provides rich context for the agent.

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, front-loaded with the core purpose, then behavior and constraints. No fluff, every sentence adds value. Well-organized for an agent to parse.

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?

Given the tool's complexity (5 params, conversion rules, constraints), the description covers all essential operational details: what can be converted, how children are handled, link visibility, one-time conversion, default title, and workspace requirement. 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% with all five parameters described. The description adds some behavioral context (e.g., title defaults, conversion rules) but doesn't add per-parameter semantics beyond what the schema already provides. It's a baseline 3 because 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?

Description states a specific verb (Convert) and resource (whiteboard element into backlog item), and differentiates types (sticky note to card/epic, frame to epic). It clearly distinguishes from sibling tools like create_card/create_epic (which create new items from scratch) and convert_mind_map (different source). The purpose is 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?

Clear context for when to use: when you have an existing whiteboard element to turn into a backlog item. It mentions constraints like 'only converted once' and the Pro/trial workspace prerequisite. However, it doesn't explicitly name alternatives or say 'when not to use' – but the purpose clarity effectively differentiates it.

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