wavexis_shadow_fill

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

Adds context beyond annotations: describes side effects (mutates input, may trigger events) and return format. No contradiction with annotations (destructive hint true matches mutation). Could mention permission requirements or reversibility.

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?

Three concise sentences: purpose, usage hint, side effects/return. No wasted words; front-loaded with key action.

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 schema provides parameter descriptions, description covers purpose, side effects, return format, and a sibling usage hint. Output schema exists so return details not needed. Complete for a focused tool.

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 0% so description must compensate. It gives context for selectors ('pierces shadow boundaries') and value ('fill...with a value'), but does not elaborate on session_id or precise selector format. Adequate but not thorough.

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?

Description clearly states verb 'Fill', resource 'input element inside a shadow DOM tree', and distinguishes from siblings like wavexis_fill and wavexis_shadow_click. It also mentions piercing shadow boundaries, specifying the unique capability.

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?

Provides explicit guidance to use wavexis_shadow_click after filling for submission/activation. Implies context of shadow DOM but lacks explicit when-not-to-use or other alternatives.

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