element_call_method

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only states that it calls a method, but does not disclose whether the call has side effects, what the return value looks like, whether arguments are passed positionally, error behavior, or any permissions/authentication requirements.

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 immediately conveys the core purpose. There is no redundant or filler content, and the most important keywords are front-loaded.

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 that this tool invokes arbitrary component methods, the description is too sparse. It lacks essential context such as return values, argument-passing conventions, restrictions on which component types support methods, and potential side effects. The presence of many similar sibling tools also increases the need for clearer differentiation.

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 67%, above the 50% threshold but not high. The schema itself describes the method parameter as '仅自定义组件可用', adding a useful constraint. However, element_id has no description, and args is only described as '方法参数' without explaining ordering or structure. The tool description does not add substantial 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 clearly states the action: calling a custom component instance method. It specifies the resource type ('自定义组件实例方法'), which helps distinguish it from generic page-level method calls, though it does not explicitly contrast with the similar sibling tool element_call_context_method.

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 is provided on when to use this tool versus alternatives. The description mentions '仅自定义组件可用' as a precondition, but it does not explain when element_call_method is preferred over element_call_context_method, page_call_method, or other call-related tools.

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