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

The description usefully discloses the write path (save=true inserts into the connected DB and may return row_id; omit/false returns markdown only), which is valuable behavioral context. But this write capability conflicts with the declared readOnlyHint=true, since save=true modifies the DB environment. The description is transparent about the conflict, so it is a conditional rather than flat contradiction, warranting 2 rather than 1.

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?

The purpose is front-loaded, followed by input constraints and then the save/return behavior, all within three terse clauses. Every element carries information and there is no padding, though the endpoint parenthetical is slightly incidental.

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?

With an output schema present, return values need not be explained, and the description covers source types, the in-memory input requirement, and the save behavior. What is missing is an explicit pairing with sibling conversion tools and a caveat about the read-only annotation being inapplicable when save=true.

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%, so both 'content' and 'save' are already documented in the schema, and the description largely restates them. It adds minor clarification ('no file, no schema_id' for content, row_id return for save), but the schema does the heavy lifting, so the baseline 3 applies.

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 states a concrete verb and resource ('Convert plain text/HTML/XML to Markdown') and even gives the backing endpoint POST /api/txt-markdown, making the tool immediately identifiable. It implicitly separates itself from file-based siblings (markdown.pdf/doc/image) by 'no file, no schema_id', though it does not explicitly name those alternatives.

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?

'content field, no file, no schema_id' conveys the in-memory string variant and steers the agent away from file/schema-based siblings, so the usage context is implied. However, it never explicitly frames when to prefer this tool over claix.agent.text, claix.extract.text, or the other claix.markdown.* tools.

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