stt_extract

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

The description discloses that the tool returns innerText or an attribute per match, and implies it operates on the current page. However, it does not mention side effects, authentication needs, rate limits, or behavior when no matches are found. With no annotations, this is a moderate disclosure.

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 a single, well-structured sentence that conveys the core functionality efficiently. However, it lacks a brief breakdown of parameters or usage hints, which would improve structure.

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?

With no output schema and no annotations, the description leaves out important details like what happens with multiple matches, the default limit, and any prerequisites. It is incomplete for a tool with three parameters.

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 description mentions 'selector' implicitly and 'attribute' explicitly (via 'or a given attribute'), but completely omits the 'limit' parameter. With 0% schema description coverage, the description fails to fully compensate.

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 extracts data from the current page using a CSS selector and returns innerText or a specified attribute. This is a specific verb+resource pair that distinguishes it from siblings like stt_click or stt_navigate.

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 guidance is provided on when to use this tool versus alternatives such as stt_evaluate or stt_snapshot. There are no exclusions, prerequisites, or context for optimal use.

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