parse-wikitext

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

Annotations already indicate read-only, non-destructive, idempotent nature. The description adds important behavioral details: HTML truncation at 50000 bytes, trailing marker, and pre-save transform matching editor preview. No contradictions.

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 well-structured sentences: first states action and outputs, second gives use cases and limitation. No redundant words; each sentence earns its place.

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?

Covers outputs, use cases, truncation behavior, and parameter behavior. Without an output schema, it partially describes the return structure but could be more precise about data types. Still sufficient for agent use.

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?

Input schema covers all parameters with descriptions (100% coverage). The description adds context that 'applyPreSaveTransform' matches editor 'Show preview' behavior, but this is marginal enhancement beyond the schema's baseline.

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 uses a specific verb ('Renders') and resource ('wikitext') and clearly contrasts with sibling tools like 'create-page' and 'update-page' by stating it does not save, making it a dry-run tool.

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 when to use ('dry-running a planned edit before create-page or update-page', 'previewing standalone wikitext') and provides guidance on handling truncation with follow-up calls.

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