drawio_codec

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

With no annotations, the description carries the full burden; it does disclose that both directions of transformation exist and that the input/output formats are compressed payload vs XML. It omits error behavior on malformed payloads, size limits, and whether the returned XML is the raw editable source, leaving moderate gaps for an unannotated tool.

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 compact sentences with the core transform front-loaded after the domain tag. Every clause is relevant, though the bracketed diagram-type list is inherited boilerplate that doesn't help an agent invoke this specific codec.

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?

With an output schema present, return values need no explanation, and the description covers both operational modes of this two-parameter tool. The only shortfall is the unexplained `text` payload semantics per mode, which is a minor gap given the output schema carries the result shape.

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 schema offers no parameter detail. The description compensates for `mode` by explaining decode and encode values (and matching the default), but says nothing about what `text` should contain in each mode (compressed payload vs raw XML), leaving the most important parameter undocumented.

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 names a specific operation pair (decode a compressed <diagram> payload to XML / encode XML to draw.io format), which is concrete and separable from siblings like drawio_create_diagram and drawio_read. The leading bracketed domain tag ('draw.io: diagrams (flowcharts, ...)') is category boilerplate rather than tool purpose, slightly diluting focus.

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 indicates the two modes and what each does, which implies when you'd pick decode vs encode, but gives no explicit when-to-use guidance relative to drawio_read or drawio_create_diagram. An agent must infer from the mode semantics alone that this is a low-level transform, not a diagram authoring/reading tool.

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