bricks_clone_page

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

With no annotations, description must fully disclose behavior. It states cloning with all data and scripts, but omits critical details like new page creation, ID changes, permission requirements, or side effects on references. Insufficient for safe invocation.

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?

Single sentence, no wasted words, front-loaded. Efficient but could be slightly expanded to include behavioral or usage context without becoming wordy.

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?

Tool involves cloning a page, likely returning a new page ID, but description does not clarify output or how to reference the clone. No output schema, so agent lacks complete context to use correctly.

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 covers both parameters with clear descriptions (Page ID to clone, Optional title for the clone). Description adds no extra meaning, meeting baseline but not exceeding.

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?

Description uses specific verb 'Clone' and resource 'page', clearly distinguishing from siblings like bricks_clone_template and bricks_create_page. It also specifies scope ('all Bricks data and scripts'), adding precision.

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?

Implies usage for cloning pages but provides no explicit when-to-use or when-not-to-use guidance, nor does it reference alternatives. Given the large sibling list, some direction would help.

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