wavexis_dom_get_attr

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

Description states 'Side effects: None; read-only' which aligns with annotations. It also details the return format (JSON string with keys), adding value beyond the readOnlyHint and idempotentHint 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 concise: three sentences covering purpose, sibling, and behavior/return. It is front-loaded and contains no filler.

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 presence of an output schema, the description's return format detail is sufficient. It covers side effects and key parameters. Missing error handling details, but overall adequate for a simple read 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?

With 0% schema description coverage, the description must compensate. It mentions 'CSS selector' and 'attribute value' but does not clarify that the 'name' parameter is the attribute name. The schema does provide some descriptions for nested parameters, but the description adds minimal extra meaning.

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 tool reads an attribute value from an element using a CSS selector. It distinguishes from sibling wavexis_dom_set_attr (write) and implies difference from wavexis_dom_get (which likely gets text).

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 explicitly mentions the write alternative (wavexis_dom_set_attr). It could improve by noting when to use this over other read tools like wavexis_dom_get, but it provides clear usage context.

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