page_set_data

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

With no annotations available, the description carries the full burden. It discloses the critical behavior that the tool directly changes data without triggering reactive updates, which is a significant side effect. However, it does not mention whether data is merged or replaced, whether the change is persistent across reloads, or any error conditions. This leaves notable gaps in behavioral disclosure.

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 main action ('修改页面渲染数据') and follows with two important behavioral details. Every word earns its place, with no fluff or repetition.

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?

The description is succinct and captures the core intent, but misses several contextual aspects: whether the data is replaced or merged, what the tool returns (though no output schema exists), and any prerequisites like the page being loaded. Given the tool's complexity (2 params, nested object) and lack of annotations, the description could provide more context to be fully self-sufficient.

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 schema covers 50% of parameters: 'data' has a description ('要改变的数据对象'), while 'page_id' has no description. The tool description adds minimal parameter context—it reinforces that data is modified but does not explain the expected structure or clarify page_id. Since coverage is at the 50% threshold and the description adds little beyond the schema, a baseline of 3 is appropriate.

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 names the verb (modify) and resource (page rendering data), and the added qualifier '直接改 data，不触发组件响应式更新' distinguishes it from sibling tools that might trigger updates or operate on elements. This makes the purpose explicit and differentiated.

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 phrase '适合调试' provides a clear context (debugging) suggesting when to use this tool. However, it does not explicitly state when not to use it or name alternative tools (e.g., element_set_data or page_call_method) for reactive updates. Thus usage guidance is present but not fully developed.

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