convert_database_format

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

No annotations are provided, so the description carries the full burden. It does disclose two genuinely useful traits — conversion goes through canmatrix and the result reports attribute loss (i.e. lossy round-tripping) — but says nothing about whether output_path is overwritten, whether the input is mutated, or what the returned report looks like. The dry_run parameter, which is a key safety behavior, is entirely absent from the description.

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?

A single compact sentence with the format list front-loaded and no wasted words. It is terse to the point of leaving required semantics uncovered, but the prose itself is efficient and well-ordered.

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?

This is a file-writing mutation tool with no annotations, no output schema, and 0% parameter coverage, so the description is the only safety and semantics source. It omits overwrite behavior, dry_run, and any description of the attribute-loss report, leaving the agent under-informed for a destructive-by-nature operation.

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% across four parameters, so the description must compensate and does not. It never explains input_path vs output_path roles, how target_format relates to the output extension, or what dry_run does — arguably the most important parameter for an agent to use safely.

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?

States a specific verb ('Convert') and enumerates the supported format set (.dbc/.dbf/.arxml/.kcd/.sym/.xlsx), which clearly distinguishes it from siblings like diff_databases or inspect_database_summary. It stops short of saying conversion direction or that format is inferred from the paths, which the schema alone leaves ambiguous.

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?

There is no guidance on when to reach for this versus diff_databases, validate_database_integrity, or generate_database_from_template. No prerequisites, no exclusions, and no mention of how target_format interacts with output_path's extension.

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