What Tisty adds to Markdown

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

With no annotations, the description carries the burden of explaining behavior. It discloses that the default result is an index, that `topic` narrows to one part, and that `all` returns the whole guide, but it does not explicitly state that the operation is read-only or describe the response format.

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 reasonably sized but somewhat convoluted and poetic, starting with background about plain Markdown before stating the core behavior. The useful information is present, but the phrasing could be more front-loaded and direct.

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 simple reference-lookup tool with complete schema coverage and no output schema, the description covers defaults, topic selection, `all`, and language choice. It is largely complete, though it could more explicitly describe the returned guide format.

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 `topic` and `lang` are already documented in the schema. The description reinforces their purpose — selecting a guide section or language — but adds little beyond the schema's own enum descriptions.

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 makes clear that the tool returns Tisty's guide to Markdown extensions, either as an index or a specific topic. It distinguishes this reference material from plain Markdown, though the phrasing is somewhat indirect rather than a direct verb-resource statement.

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?

It explicitly says plain Markdown needs nothing from this tool and directs the agent to use `topic` for the specific syntax being written, with `all` for the whole guide. It does not name sibling alternatives, but the when-to-use and when-not-to-use guidance is clear.

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