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

No annotations exist, so the description carries the behavioral burden. It discloses that 'basic' quality checks attach local output-health checks in the quality field and that 'ai' sends selected excerpts to TypeSafe, which is useful privacy/behavioral context. It stops short of describing error handling or output shape, but the main side effects are covered.

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?

Three tight paragraphs front-load the core operation, then add routing guidance and parameter detail. No filler or redundancy.

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 conversion tool with no output schema or annotations, the description covers purpose, the key input semantics, routing, and the quality field. It does not spell out the final return envelope or failure modes, but nothing essential to invoking the tool correctly is missing.

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 has zero parameter descriptions, so the description must compensate. It explains filename's role in format detection, implies content_base64 from the first sentence, and details quality_check values and defaults. This covers all three parameters, though content_base64 could be more explicit.

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 opening sentence uses a specific verb ('Convert') and object ('base64-encoded file contents to Markdown'), and the reference to filename-driven format detection further defines scope. It also distinguishes itself from convert_url by naming the sibling, so an agent can disambiguate.

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?

Explicitly states intended context ('programmatic MCP clients') and tells the agent to prefer convert_url for anything with a URL. Qualifies the quality_check parameter with exact behavior for 'basic' vs 'ai', giving clear selection criteria.

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