pbi_duplicate_visual

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

No annotations are provided, so the description carries the full burden. It discloses that only the identifier is regenerated, the copy is offset to avoid overlapping, and target_page allows copying to another page. This adds meaningful behavioral context, though it omits details about permissions, error handling, or interactions.

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 four short, focused sentences. Each sentence adds unique information: purpose, identifier regeneration, offset behavior, and target_page. No redundancy or fluff.

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?

The description covers core behavior and key parameters, and an output schema exists to explain return values. However, with no annotations and 7 parameters, the lack of new_title/request_id explanations and absence of usage prerequisites make it incomplete for fully informed invocation.

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 offset_x/offset_y and target_page, but does not cover new_title or request_id. Page and visual_id are implied but not explicitly described. This partial coverage leaves some parameters under-explained.

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 opens with 'Duplica un visual conservando campos, formato y filtros', clearly stating the action (duplicate) and resource (visual), and specifies preserved attributes. This distinguishes it from siblings like pbi_delete_visual or pbi_copy_visual_format.

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 when to use the tool (to duplicate a visual with preserved properties) and provides context about offsets and target_page, but does not explicitly mention alternatives such as pbi_create_visual or pbi_copy_visual_format, nor any exclusions or when not to use it.

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