sleeper_read

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

With no annotations and no output schema, the description carries the full behavioral burden, yet it says nothing about return format, error behavior when the selector matches nothing or multiple nodes, or how the mode changes the result. It only restates the operation the name already conveys.

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 single parenthetical phrase is front-loaded and wastes no words, but its extreme brevity reflects under-specification rather than disciplined conciseness given the tool's five parameters.

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 five-parameter tool with no annotations and no output schema, the description omits far too much: the output structure, the attr/what dependency, tab scoping, and selector behavior. An agent cannot call this confidently across all modes without opening the schema and guessing.

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 only 20% (just the profile param). The description lists the values for 'what' (text/html/value/attr), but those already appear as the schema enum, and it says nothing about tab, attr (which is clearly required when what=attr, an unstated dependency), or selector matching semantics.

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?

States a specific verb+resource (read a single element) and enumerates the four extraction modes (text/html/value/attr). The word 'single' implicitly distinguishes it from the sibling sleeper_read_all, but it never names that alternative, so the differentiation is only implied rather than explicit.

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?

No when-to-use guidance and no mention of alternatives. The word 'single' hints that sleeper_read_all handles bulk reads, and the several other read-oriented siblings (sleeper_get, sleeper_find, sleeper_extract) are unaddressed, leaving the agent to infer routing.

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