page_callMethod

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

With no annotations provided, the description discloses key behaviors: the call is awaited, args are positional, return structure includes method/arguments/result, and errors return UserError. However, it does not mention potential side effects on page state, though this might be implicit for method calls.

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 concise (about 120 characters) and front-loads the main action. It could be more structured, but it avoids redundancy and waste.

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 no output schema, the description covers the return structure and error handling. It distinguishes from sibling tools and explains usage context. Missing details on maxBytes and connection semantics slightly reduce completeness.

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 only 25% (only connection field described). The description adds meaning: args are positional (not named), method is the method name. But it does not explain maxBytes or connection in detail beyond the schema, leaving some parameters under-documented.

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 'calls a method exposed on the current page instance' and explicitly distinguishes from the sibling 'element_callMethod' for component instances. The verb 'call' and resource 'page method' are specific.

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 provides explicit guidance: use when triggering real page logic (better than page_setData) and use element_callMethod for component methods. It also mentions error handling with UserError for missing methods or internal errors.

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