Designer Element Tool

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

Annotations indicate readOnlyHint=false and openWorldHint=true, so the tool is not read-only. The description says 'perform actions' which implies changes, but it does not explicitly disclose the presence of dangerous actions like 'remove_element' (marked DANGEROUS in the schema). The tool description adds minimal behavioral context beyond the annotations.

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 a single sentence, which is concise but too brief to be useful. Important information about the tool's capabilities is omitted. Conciseness should not sacrifice completeness; here it does.

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 the tool's complexity (many actions, required siteId, nested objects), the description is woefully incomplete. It does not explain the return value, does not hint at the depth of functionality, and does not prepare the agent for the complex input schema. The annotations provide minimal context, and the description fails to fill the gap.

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 50%, meaning many parameters lack descriptions. The tool description does not add any meaning for parameters; it only lists a few action types without explaining their structure or the required `siteId` and `actions` parameters. For example, it does not clarify that `actions` is an array of action objects with multiple specific types.

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 states it is a 'Designer Element Tool to perform actions like get all elements, get selected element, select element on current active page. and more.' It gives a general sense of the tool's purpose but does not specify all actions (e.g., mutations like remove_element, set_text) and does not differentiate from sibling tools like element_builder or style_tool. The verb 'perform actions' is vague.

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 versus alternatives. The description does not mention prerequisites (e.g., need a siteId, need an active page) or when not to use it. The schema's siteId property has a detailed instruction to ask user for siteId, but that is not in the tool description itself.

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