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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered, and the description adds that results are slugs rather than full converter objects. It does not mention whether the catalog is cached, how many results come back, or how matching works. No contradiction with openWorldHint despite the word 'live'.

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?

A single front-loaded sentence with zero filler, and the slug examples earn their place by showing the exact output format an agent should expect.

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?

An output schema exists, so return values need not be explained, but the description does nothing to cover its two undocumented parameters and offers no routing guidance against the three siblings. Adequate to call the tool, not adequate to call it well.

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 0%, so both parameters (limit, search) are undocumented anywhere except their titles and defaults. The description's use of the verb 'Search' faintly gestures at the search param but gives no guidance on matching semantics, while the limit parameter and its 1-100 cap are never mentioned.

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 and resource ('Search the live XML.now converter catalog') and clarifies the return type with concrete slug examples (xml-to-json, xml-to-csv). It is distinguishable from siblings by resource, though it never explicitly contrasts itself with convert_image_url or get_conversion_status.

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?

Usage is only implied: returning 'valid converter slugs' hints that this is a discovery step before calling a conversion tool, but the description never states when to use it, when not to, or which sibling to prefer. No prerequisites or exclusions are given.

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