run_conversion

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

Annotations are absent, so the description carries the full burden. It only mentions 'return conversion output information' but does not disclose side effects (e.g., file modification, overwriting), authentication needs, error behavior, or whether the command is read-only. This is insufficient for a tool that 'runs' a command, implying execution with potential side effects.

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 one concise sentence, front-loaded with the action ('Run a conversion command') and the result ('return conversion output information'). There is no filler or redundancy, making it appropriately sized for the tool's 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?

With no annotations, no output schema, and 5 parameters including a nested options object, the description is not complete enough. It does not explain the expected output format, the semantics of options, or how inputs are provided. An agent would likely need additional context to call this tool correctly.

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 the baseline is 3. The description adds no meaning beyond the schema: it does not clarify the relationship between input_path and input_content, the meaning of the options object, or when to use which parameter. However, the schema already provides basic descriptions for each parameter, so no penalty beyond baseline.

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 states a specific action ('Run a conversion command') and what it returns ('conversion output information'). It clearly distinguishes from siblings by the verb 'run' versus 'list', 'get', or 'describe', though it doesn't explicitly name alternatives or explain what a 'conversion command' is in this context.

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 tool versus the siblings (list_conversions, get_conversion, describe_capabilities). The description does not mention prerequisites, input selection (path vs content), or when alternatives are more appropriate. There is no explicit 'when-to-use' or 'when-not-to-use' context.

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