wavexis_dom_get_attr

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the return format (JSON with value, selector, name) but does not disclose behavior for missing element, multiple matches, or error handling. It provides some added context but not fully transparent.

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 extremely concise: two sentences covering purpose, parameters, and return value. No redundant information.

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 tool simplicity (one parameter object with three fields), annotations present, and output schema exists, the description covers the core behavior and return format. However, it lacks information on error cases or behavior with invalid selectors. Still largely adequate.

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 0% for the three sub-parameters. The description only mentions 'selector' and 'name' in a brief note ('Attribute parameters (selector, name)'), omitting session_id entirely. This adds minimal value 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 verb 'Get' and the resource 'attribute value from an element matching a CSS selector'. It is specific and distinguishes from siblings like wavexis_dom_set_attr and wavexis_dom_remove_attr.

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 implies usage for reading an attribute but lacks explicit guidance on when to use this tool versus alternatives like wavexis_dom_get or wavexis_dom_query. No when-not-to-use or alternative naming is provided.

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