Add Layout Legend

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

The description discloses that the legend is linked to a map item (defaulting to the first) and that position/size are in mm. However, it does not clarify error handling (e.g., missing layout), side effects, or whether the legend replaces existing ones. With no annotations, more detail would be beneficial.

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 description is two sentences with no unnecessary words. Essential information (purpose, default behavior, units) is front-loaded and clear.

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 provides a decent overview but omits details on layout_name (required), title purpose, and coordinate origin. It is adequate for basic understanding but not fully thorough.

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?

With 0% schema description coverage, the description partially compensates by explaining map_item_id defaults and that x, y, width, height are in mm. However, title and layout_name are not elaborated, leaving ambiguity for 2 out of 7 parameters.

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 the verb 'add', the resource 'legend to a print layout', and key details like linking to a map item and dimensions in mm. It effectively distinguishes from sibling tools dealing with other layout elements.

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?

Usage context is implied (adding a legend) but no explicit guidance on when to use this tool versus alternatives like add_layout_label or add_layout_scalebar. No exclusions or prerequisites mentioned.

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