Data Scripts Tool

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

Annotations indicate readOnlyHint=false and openWorldHint=true. The description adds no behavioral details beyond stating actions, such as the destructive nature of deletions or replacement behavior of upsert. It does not contradict annotations, but provides minimal added context.

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, concise but not well-structured. It front-loads the tool's nature but lists examples incompletely, and does not prioritize key information. It is adequate but could be more organized.

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 (multiple actions for both sites and pages) and lack of output schema, the description is insufficient. It omits page-related actions and does not explain the workflow between actions, leaving significant gaps for an agent.

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?

The description does not describe the 'actions' parameter or its sub-properties, despite the schema having detailed descriptions. With 0% schema description coverage, the description fails to compensate, offering no added meaning 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 states it is a scripts tool that performs actions like listing and adding scripts, but it does not cover all actions in the schema (e.g., page script actions) and uses 'like', making it vague. It distinguishes from other tools by its name but lacks specificity.

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 sibling tools such as data_cms_tool or other data tools. The description only labels it as a 'Data tool - Scripts tool' without any context on alternatives or prerequisites.

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