get_page_item_script_labels

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It states the operation is read-only, which is implicit, but fails to detail any side effects, permissions, return format, or constraints. This is inadequate for an agent to understand the full impact of invoking the tool.

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 that conveys the core purpose without any superfluous words. It is front-loaded and efficient, earning its place with no redundancy.

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 has 5 optional parameters, multiple modes, and no output schema, the description is too sparse. It does not explain what script labels are, the format of return values, or any usage constraints. An agent would need to infer significant details from parameter names alone, which is insufficient for a tool of this complexity.

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 coverage is 100% and parameter descriptions are already detailed. The description adds context by linking the mode parameter to 'selection or explicit identifiers', but this is a modest addition. The baseline of 3 is appropriate as the description does not significantly enhance understanding beyond the schema.

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 'read' and the resource 'script labels from page items', and mentions the method 'using selection or explicit identifiers'. This distinguishes it from sibling tools like set_page_item_script_label, making the purpose highly specific and unambiguous.

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 through the mention of selection or explicit identifiers, but does not explicitly state when to use this tool versus alternatives (e.g., set_page_item_script_label for writing). No when-not or prerequisite information is provided, leaving the agent with minimal guidance.

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