Add Layout Legend

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

With no annotations, the description must disclose behavioral traits. It only mentions adding a legend with position/size in mm, but omits behavior on missing layout, invalid map item, or whether the legend replaces an existing one. No return value or error handling info.

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?

One sentence, efficient and front-loaded with action and key details. Could benefit from brevity in listing mm but overall concise.

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?

Given 7 parameters, no output schema, and no annotations, the description is too brief. It lacks details on return values, error conditions, and prerequisites for a complete understanding.

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 has 0% description coverage. The description adds meaning to x, y, width, height (position/size in mm) and clarifies map_item_id defaults to first map item. This adds value beyond the schema but does not cover all parameters (e.g., title, layout_name).

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 clearly states it adds a legend to a print layout, linking to a map item, with position/size in mm. It distinguishes from sibling tools like add_layout_label and add_layout_map by specifying 'legend'.

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?

No guidance on when to use this tool vs alternatives, nor prerequisites like requiring an existing layout or map item. The description implicitly suggests a map item should exist but does not state explicitly.

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