docconvert_text

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

No annotations are provided, so the description carries full burden. It mentions 'Lightweight' but does not disclose limitations, error handling, idempotency, or output format characteristics. This is insufficient for a tool with no safety profile.

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 description is very concise (one short sentence) and front-loads cost and purpose. However, it could be structured to separate cost, purpose, and examples. Still, it efficiently conveys core information.

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?

Given the tool has 3 unannotated parameters, no output schema, and no sibling differentiation, the description is incomplete. It lacks details on allowed values, error behavior, content size limits, and result format, which are critical for correct invocation.

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?

With 0% schema description coverage, the description should compensate. It hints that 'from' and 'to' take format strings (e.g., md, html, json, csv) but does not list accepted values, provide examples, or clarify constraints. 'content' is self-explanatory but still under-specified.

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 clearly states the tool performs format conversion between specific formats (md↔html, json↳csv) and uses verbs like 'transcoding'. It differentiates from sibling tools like docconvert_pdf by stating 'Lightweight content transcoding', implying text-based conversions.

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 description includes a cost hint ('[$0.001 USDC]') which guides cost-aware usage, and implies formats by listing examples. However, it does not explicitly state when to use this tool vs alternatives like docconvert_pdf, or provide exclusion criteria.

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