Edtb Mxl Decompile

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 communicates that this is a conversion operation and names the output format, but it does not disclose side effects such as file writes, overwriting behavior, projectPath resolution, or whether the operation is read-only. These are significant behavioral gaps.

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 a single sentence with no filler or redundant phrasing. The core operation is stated directly and front-loaded, making it easy to parse quickly.

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?

Although an output schema exists, the overall definition is incomplete. There are no annotations, parameter documentation, or usage context, so the description does not provide enough information to select and invoke the tool correctly. The optional projectPath, required fields, and side-effect behavior are left unexplained.

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?

The input schema has 0% description coverage, so the description must compensate. It does not explain what objectName, templateName, or projectPath mean, how they relate to the .mxl artifact, or what values are expected. An agent cannot reliably determine how to fill the required parameters from the description alone.

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 names the verb 'декомпилировать' (decompile), the resource (a .mxl layout of a project), and the output format (JSON-DSL). This makes the tool's purpose distinct from siblings like edtb_mxl_compile, which performs the inverse operation.

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 about when to use this tool versus alternatives such as edtb_mxl_info or edtb_mxl_compile. There is no mention of prerequisites, workflow context, or conditions that should lead an agent to choose this tool.

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