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

Annotations only declare readOnlyHint=false, openWorldHint=false, destructiveHint=false. The description adds a helpful disambiguation warning, but does not clarify whether the operation is a pure in-memory conversion with no side effects or whether it writes output somewhere. Given readOnlyHint=false, the agent is left uncertain about side-effect behavior, though destructiveHint=false rules out destructive actions.

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 efficient sentences deliver the core purpose, supported conversions, and critical parameter notes. The information is front-loaded and every clause earns its place. The trailing [category: convert] tag is minor metadata and does not add noise.

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 simple three-parameter converter with full schema coverage, the description covers the essential invocation details and supported pairs. It could be more complete by explicitly stating the return value (converted text in target format) and clarifying when to use alternative convert tools, but the current level is sufficient for correct basic invocation.

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 the baseline is 3. The description adds value by explicitly confirming the parameter names ('text', 'from', 'to') and warning that there is no 'conversion_type' field — a highly useful guard against a common hallucinated parameter. It also confirms that encode/decode operations ride in 'from', reinforcing the schema.

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 uses a specific verb (Convert) and resource (text/data formats), then enumerates the supported conversions (Markdown↔HTML, CSV↔JSON, JSON↔XML/YAML, Base64/URL encode-decode). This makes the tool's purpose unmistakable and distinguishes it from file-oriented siblings like convert_file or convert_archive by explicitly limiting scope to text/data formats.

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?

The description implies usage through the supported format list and required parameters, but never explicitly states when to prefer this tool over the many similar convert_* siblings (e.g., convert_data, convert_document, convert_file). It gives no when-not-to-use guidance or alternative routing, so an agent must infer the boundary from the format list alone.

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