convert_to_confluence

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

Annotations declare idempotentHint=true and non-destructive behavior. Description adds value by specifying exact output format quirks ({info}, {note}, {code} macros) that pure schema doesn't cover. Does not address file I/O side effects (covered in schema) or error behaviors.

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, zero waste. First_sentence establishes operation, second_sentence provides critical sibling differentiation and output format specifics. Every word 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?

Adequate for a conversion utility with simple I/O. Covers core functionality and format-specific features. Lacks error handling documentation or edge case notes (e.g., unsupported Markdown extensions), but acceptable given idempotentHint and full schema coverage.

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 coverage is 100% with detailed descriptions for both 'markdown' (GFM support details) and 'output_path' (file vs return behavior). Description provides no additional parameter syntax guidance, meeting baseline expectation when schema is comprehensive.

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?

Clear specific verb 'Convert' + resource 'Markdown/Confluence wiki markup'. Explicitly distinguishes from sibling 'convert_to_jira' by contrasting Confluence-specific panels vs JIRA syntax, preventing selection errors.

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?

Implicitly guides selection by stating 'Similar to JIRA but includes Confluence-specific...' which signals the differentiation point. However, lacks explicit 'use when targeting Confluence vs JIRA' directive or exclusion criteria.

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