convert_machine_format

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

No annotations are provided. The description adds that conversion is 'direct' and format is from extension, but fails to disclose potential issues like overwriting, supported formats, permissions, or error handling. Minimal behavioral context beyond basic operation.

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 with zero wasted words. The core action is front-loaded, followed by a clarifying example and a crucial detail about format inference. Every sentence serves a purpose.

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?

The description minimally covers the tool's function given its simplicity (2 string params, no output schema). However, it lacks completeness on return values, error cases, and format support, leaving gaps for an agent to fully understand tool behavior.

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 0%, so description must explain parameters. It provides no per-parameter details; only indirectly clarifies input_path and output_path via the example. The agent gains little extra meaning beyond the schema field names.

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 verb 'convert' and the specific resource 'machine embroidery file', with an explicit example (dst to pes) that distinguishes it from sibling tools like import/export or listing formats. The note about format taken from output extension adds precision.

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?

The description implies when to use (to change format), but does not explicitly state when not to use or mention alternatives like list_formats or import/export. No exclusion criteria or context for agent to differentiate.

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