page_call_method

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

No annotations are provided, so the description carries the full burden for disclosing side effects, prerequisites, return values, or error behavior. It only describes the action (calling a method) without any warning about potential side effects or what happens after invocation, leaving significant transparency gaps.

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 in Chinese that clearly states the tool's function and includes helpful examples. It is front-loaded with the main verb and resource, with no unnecessary words or 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?

For a tool with no annotations, no output schema, and a moderately complex action (method invocation), the description is too sparse. It does not mention return values, error handling, or whether the call may trigger side effects, leaving the agent with insufficient context to fully understand the tool's behavior.

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 adds no parameter-level information. The schema already covers 'method' and 'args' with descriptions, but 'page_id' is undocumented in both schema and description. Since schema coverage is only 67% and the tool description provides no further clarification, the description fails to compensate for the missing parameter details.

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 tool's purpose: '调用页面实例方法' (invoke page instance methods). It provides concrete examples (onPullDownRefresh, custom methods) and distinguishes this tool from siblings like element_call_method or call_wx_method by explicitly focusing on page instance methods.

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 gives context by indicating it covers event methods and custom methods, but it does not explicitly state when to use this tool over alternatives (e.g., element_call_method) or provide any exclusions. Usage is implied rather than explicitly guided.

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