wavexis_dom_set_attr

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

Annotations indicate idempotentHint=true and destructiveHint=false. The description adds value by explicitly stating 'Mutates the DOM by writing the attribute on the matched element' and outlining the return format as a JSON string with status keys. It clarifies the mutation behavior beyond annotations.

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 three concise sentences. The first sentence front-loads the primary action, the second provides a usage hint, and the third covers side effects and return. No redundant or unnecessary content.

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 simple set-attribute operation, the description covers the operation, side effects, and return format. It does not explain error conditions or prerequisites, but the schema covers the session_id requirement. The output schema is described adequately. Overall, it is complete for the tool's complexity.

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 schema already provides descriptions for all four parameters (name, value, selector, session_id). The description does not add new information about the parameters beyond implying the selector is a CSS selector, which is already in the schema. Baseline 3 is appropriate given high 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 the verb 'Set', the resource 'attribute on an element', and the method 'CSS selector'. It explicitly distinguishes from the sibling tool 'wavexis_dom_get_attr' by recommending its use for reading before setting.

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 advises using 'wavexis_dom_get_attr' to read the current value before setting, providing clear context for when to use this tool and a direct alternative. It does not explicitly list when not to use it, but the guidance is sufficient for an AI agent.

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