element_getWxml

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

No annotations are provided, so the description carries full burden. It discloses truncation behavior (returns {truncated, bytes, maxBytes, note, data} when exceeding maxBytes), notes that WXML is most likely to exceed, and describes default vs outer behavior. It does not discuss performance or auth, but for a read operation this is sufficient.

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 and front-loads the main purpose. It uses a few sentences to cover key details. While it could be more structured (e.g., bullet points), it is efficient and earns its sentences.

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 parameter complexity (5 params, 1 required, nested object) and no output schema, the description covers the main behavioral aspects: inner vs outer WXML, custom components, and truncation. It does not detail the output format beyond the truncation case, but it provides enough for an agent to select and invoke the tool correctly.

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 only 20% (only connection object has a description). The description adds significant meaning: explains outer parameter effect, maxBytes default and truncation handling, selector usage with [index=N] syntax, and innerSelector for custom components. This compensates well for the low schema coverage.

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 '获取元素 WXML' (get element WXML), specifying the verb and resource. It distinguishes between internal WXML (default) and outer WXML (with outer=true), and addresses custom component WXML via innerSelector, differentiating it from sibling tools that handle other element properties.

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 on when to use outer=true vs default, when to use innerSelector for custom components, and how to handle truncation (use more specific selector or increase maxBytes). It does not explicitly state when not to use this tool, but the scenarios are well-covered.

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