Transform

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that the operation downloads (consistent with openWorldHint) and converts into Fluent source, clarifying the transform direction. It omits where output lands, whether existing files are overwritten, and any auth requirements.

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 front-loaded sentence with zero filler, naming the operation and the command form. It is efficient but so terse that it leaves the tool under-explained for its 2-parameter surface.

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?

For a tool that mutates filesystem/project state with two undocumented parameters and no output schema, the description is too thin: it omits auth needs, working directory, overwrite behavior, and result format. Only the core transformation is conveyed.

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% for two opaque parameters (params, params_json), and the description adds no meaning about what they accept or how they map to the transform. The agent gets no guidance on the JSON payload shape beyond what an empty schema reveals.

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 concrete compound verb (download + convert) and the transformation target (XML records into Fluent source), plus the backing CLI command. This is clearly more than a tautology. It does not differentiate from sibling SDK tools like sdk_build or sdk_deploy, so it falls short of a 5.

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 when-to-use guidance, no prerequisites, and no mention of alternatives among the numerous SDK siblings (sdk_init, sdk_build, sdk_deploy). The only usage cue is the parenthetical CLI command, which implies but does not state context.

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