ass_join_drawings

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

With no annotations, the description carries the full burden and does disclose real behavior: every part must parse, empty strings are rejected so no subpath is silently lost, and coordinates are serialised as integers. It also enumerates the return payload. It does not state side effects or whether the operation touches the document beyond returning doc_id, leaving a modest gap.

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?

Front-loads the core action, then adds validation and return details in compact, well-organized sentences with no filler. Every sentence earns its place.

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?

An output schema exists, so return-value explanation is redundant but harmless. For a two-parameter transformation tool the description is nearly complete, with the only real omission being any explanation of the doc_id parameter.

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 description must compensate. It explains 'parts' well (list of drawing strings, single string coerced to a one-element list) but says nothing about 'doc_id', leaving one of the two parameters undocumented in both schema and description.

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?

States a specific verb ('join') and resource ('drawing strings') and explicitly positions itself as the inverse of the sibling ass_split_drawing. An agent can distinguish it from ass_split_drawing, ass_transform_drawing, and ass_scale_drawing without opening a schema.

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 inverse-of-ass_split_drawing framing gives clear context for when this tool applies, and the note that a single string is treated as a one-element list clarifies accepted input shapes. It stops short of naming exclusions or an alternative to pick when the parts don't parse, so it is clear but not exhaustive.

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