mc_kit_image

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

No annotations are provided, so the description carries the behavioral burden; it does disclose the default output directory, inline image return, and the publish area path. However, it does not explain overwrite behavior, error handling, or permission/rate constraints for save or render.

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 definition front-loads the key idea that SVG is the editing language, then uses a compact action list with no obvious filler. The length is justified by five actions, output behavior, and publish routing.

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 14-parameter multi-action tool with no annotations or output schema, the description covers each action's purpose and return/publish behavior well enough for selection and invocation. It still stops short of side-effect details for save/render and formal return shapes.

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 coverage is 100%, so the baseline is 3, but the description adds useful action-level constraints such as svg and svgPath being mutually exclusive and width/height/scale being render options. Most individual parameters are still left to the schema, but the added routing semantics go beyond the structured fields.

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 image toolkit and enumerates five specific actions (info/embed/render/grid/save), with SVG rasterization and grid composition as the core model. It also distinguishes the publish retrieval path by naming mc_kit_express, so the tool's role is clear against nearby siblings.

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?

It gives clear per-action guidance, including that embed is mandatory for referencing images inside SVG and that render takes either svg text or svgPath. It also explains the default output location and publish flow through mc_kit_express, though it does not explicitly say when not to use the tool overall.

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