Get esa Markdown syntax documentation

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

Annotations already declare readOnlyHint=true. The description adds that it is a preparatory step for other tools, reinforcing its safe, read-only nature. No contradictions; additional context about its role in the workflow is provided.

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: first states purpose, second provides usage guidance. Every sentence adds value without redundancy. Front-loaded with the action, no wasted words.

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 simplicity (no parameters, no output schema), the description is complete. It states what it does, when to use it, and references sibling tools. Could mention what form the documentation takes, but not necessary for correctness.

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?

No parameters exist, and schema coverage is 100%. The description correctly adds no parameter info since there are none. Baseline for zero-parameter tools is 4, and the description meets it without needing to compensate.

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 retrieves Markdown and formatting documentation when unsure about syntax. It distinguishes itself from sibling tools by specifying it's a help resource for tools with *_md parameters, using concrete examples.

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?

Explicit usage guidance: 'Use this BEFORE using any tools with *_md parameters' and lists specific tools (esa_create_post, etc.). Also specifies the condition: 'if you need clarification on Markdown syntax, esa-specific extensions, or formatting options.' This provides clear when-to-use and implied when-not.

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