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

The description is genuinely transparent about the optional write path ('save=true inserts into the connected DB... may return row_id'), which the annotations do not capture. However, this disclosed DB insert directly conflicts with the declared readOnlyHint=true, so the description and annotations are inconsistent; the transparency is real but the conflict prevents a higher score.

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, front-loaded with the action and endpoint, with no filler. It is dense with parenthetical detail but every clause (endpoint, no schema_id, save semantics) carries information an agent needs.

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 and all inputs are schema-documented, so return values and input formats need not be restated. The description covers the endpoint, the optional persistence path, and the absence of schema_id, leaving it essentially complete for a low-complexity conversion tool, though the readOnlyHint conflict slightly undercuts it.

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 100% and all five parameters are documented in-schema, so the baseline is 3. The description echoes the save semantics already in the schema and adds the 'No schema_id' clarification, but contributes no syntax or format detail beyond the structured fields.

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+resource ('Convert image to Markdown') and even names the backing endpoint (POST /api/img-markdown), so the agent knows exactly what it does. It is distinguishable from siblings via 'image' in the name/title, but the description itself never differentiates it from claix.markdown.pdf/.doc/.audio or claix.extract.image, so it stops short of a 5.

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 'No schema_id' note is a weak differentiator versus schema-driven siblings, and the save=true/false semantics describe behavior rather than when to pick this tool. There is no explicit 'use this instead of X when Y' guidance, so an agent must infer routing from the tool name alone.

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