convert_cdm_to_pdm

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

With no annotations, the description carries the behavioral disclosure burden. It does add meaningful context by revealing a two-step strategy: native conversion first, then structured mapping as fallback. But it does not disclose whether the conversion mutates the source model, creates a new model, or what output/result the agent should expect.

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 very short and front-loaded. The core action is stated first, the optional parameter is parenthesized, and the fallback strategy is a single second sentence. Every phrase 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?

The tool has no output schema and no annotations, so the description must cover conversion behavior and return semantics. It explains the basic purpose and dbms input, but omits whether the conversion is in-place, whether a new model is produced, and what a successful conversion returns. This is a significant gap for a conversion tool.

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 the description must compensate for both parameters. It explains dbms with an example, but it never describes model_id, which is the only required parameter. The name alone is suggestive, but not enough for an agent to know what the model ID refers to.

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 verb ('Convert') and resource ('a CDM model to a PDM'), and it clearly distinguishes this tool from siblings like convert_ldm_to_pdm and convert_cdm_to_ldm by naming the source and target model types. The optional dbms note adds useful scope.

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 the obvious use case from the tool name and gives one explicit usage hint: optionally pass a dbms value such as 'MySQL 5.0'. However, it does not explain when to prefer this tool over sibling conversion tools or when the fallback path would apply.

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