convert_with_pandoc_advanced

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

With no annotations, the description carries full burden for behavioral disclosure. It lists parameters but does not disclose side effects (e.g., file overwrites), required permissions, or error conditions beyond 'error message'. Key behavioral traits like destructive potential are omitted.

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 front-loaded with a clear one-line summary, followed by a concise bullet list of parameters with brief explanations. It is not verbose and efficiently covers all parameters, though the bullet format is straightforward rather than polished.

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's complexity and the lack of annotations, the description misses key contextual elements: no usage guidance, no behavioral transparency, and no explanation of return values (though output schema exists). The agent would need additional knowledge to use this tool correctly alongside its many siblings.

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?

Despite 0% schema description coverage, the description adds meaningful context for all 13 parameters, explaining their purpose (e.g., 'Input file path', 'Pandoc input format (optional, auto-detect by extension)'). This compensates for the schema gap, though some parameters lack example values or constraints.

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 it is for 'Advanced Pandoc conversion' and lists capabilities like filters, defaults, metadata, variables, and custom PDF engine. This distinguishes it from simpler conversion tools among siblings. However, it does not explicitly state the core conversion action in a standalone verb-resource phrase.

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?

No guidance is given on when to use this advanced tool versus simpler alternatives like convert_document or convert_markdown_to_docx. The description implies 'advanced' use but does not specify conditions or exclusions, leaving the agent without clear decision criteria.

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