set_page_item_script_label

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

With no annotations, the description must fully disclose behavior. It indicates the action is destructive ('overwrite') but omits details like reversibility, permissions, error handling, or the effect of clearing the label (empty string). The schema provides some details, but the description adds little beyond the purpose.

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, concise sentence that front-loads the key action and resource. It could be slightly more informative without being verbose, but it is efficient.

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 complexity of the tool (6 parameters, multiple selection modes) and lack of output schema or annotations, the description is incomplete. It does not explain the modes or provide usage context, though the schema fills some gaps.

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 100%, so the schema documents each parameter adequately. The tool description adds no additional parameter-level information, meeting the baseline of 3.

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 'Overwrite the script label for targeted page items' clearly identifies the action (overwrite), resource (script label), and target (page items). It distinguishes from sibling tools like get_page_item_script_labels by specifying an overwrite operation, but it could be more specific about the 'targeted' aspect which is handled by parameters.

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 is provided on when to use this tool versus alternatives like set_page_item_properties or apply_object_style. It does not mention the get counterpart or explain which mode to choose for different scenarios.

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