elements_flatten_transform

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

Annotations only declare destructiveHint=true; the description adds real value by explaining what mutation occurs (transforms are replaced by baked geometry) and that unsupported inputs are rejected rather than silently altering SVG semantics. It does not disclose the revision-guard/concurrency behavior implied by expectedRevision.

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?

Two tightly written sentences, front-loaded with the core action and followed by the constraint. Every clause earns its place with no filler.

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?

Output schema exists so return values need no explanation, and the operation semantics are well covered. But for a destructive batch tool with four undocumented required parameters and a maxItems=100 constraint, the description leaves important operational context unaddressed.

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 4 required parameters, so the description must carry the burden and it does not. It says nothing about ids, path, workspaceId, or the optimistic-concurrency expectedRevision token, leaving an agent with no meaning beyond raw patterns.

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?

Names a specific verb (bakes) and resource (axis-aligned translate/scale/matrix transforms) and states the outcome (safe primitive geometry). An agent can distinguish it from elements_transform and paths_flatten by the 'own axis-aligned' scope, though no sibling is named explicitly.

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 rejection list (rotation, skew, paths, inherited transforms) functions as implicit when-not-to-use guidance, which is genuinely useful. However, it never says when to prefer this over siblings like elements_transform or paths_flatten, so the routing decision is left to inference.

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