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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and world-boundedness are covered structurally. The description adds that the catalog is 'live' and that results are guaranteed valid slugs, which is genuinely useful context, but there is a mild tension between 'live' remote catalog and openWorldHint=false that goes unaddressed.

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 no wasted framing; the slug examples are legitimately useful for recognition. Slightly padded by the four-item example list, but it earns its length.

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-value details are rightly omitted, and the tool itself is a simple two-parameter list operation. However, with zero schema coverage, the description leaves pagination limits and search matching behavior unexplained, which an agent needs 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 the description must carry parameter meaning and does not: neither 'limit' (1-100, default 50) nor 'search' (free-text matching behavior) is explained. Only a loose hint at searching exists, leaving both parameters undocumented in prose.

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 PPT.now converter catalog') and clarifies the return type ('valid converter slugs'), with concrete examples like ppt-to-pdf. It implicitly separates discovery from the sibling conversion tools, but never names them explicitly.

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: an agent can infer this is a discovery/lookup step to obtain slugs before calling convert_image_url or a conversion endpoint. There is no explicit statement of when to use this versus the siblings, nor any prerequisite or exclusion.

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