Add Layout Scale Bar

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

No annotations are provided. The description only states the action and style examples, but does not disclose error behavior, what happens if the layout is missing, or whether it modifies existing scale bars. Transparency is low.

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 and efficiently states purpose and style examples. It is front-loaded and contains no redundant information, though a bit more detail on parameters would not hurt conciseness.

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 sparse. It does not explain what the tool returns (if anything), error conditions, or how the scale bar integrates with the layout. Important contextual information is missing.

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 adds minimal meaning beyond schema. It mentions 'style' and links to map item, but does not explain x, y, width, height, layout_name, or map_item_id. The schema defaults exist but are not described.

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' and the resource 'scale bar to a print layout', and specifies it is linked to a map item. This distinguishes it from other add_layout_* siblings by focusing on a scale bar specifically.

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 description implies usage when adding a scale bar to a layout, but does not mention prerequisites (e.g., layout must exist) or when not to use it. No alternative tools are discussed, so guidance is minimal.

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