element_query_all

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

With no annotations provided, the description carries the full burden. It discloses the return type (array of element_id handles) and the important limit of 1000 handles, along with the behavior of keeping only the last 1000. This goes beyond the schema and provides useful behavioral context, though it does not explicitly mention read-only semantics or error cases.

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 includes the core action, the scope (within element), the selector type, the return type, and the limit. Every word contributes relevant information without redundancy.

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's simplicity, the description covers the key aspects: purpose, parameters, return value, and a critical limit. The lack of an output schema increases the burden to explain returns, which the description does. It omits minor details like empty array behavior and result ordering, but these are not critical for effective use.

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 provides a description for 'selector' (WXSS selector) but not for 'element_id'. The description clarifies that element_id refers to the element within which the query occurs, adding meaning to that parameter. However, it does not provide detailed syntax or examples for the selector, so the added value is moderate, given only 50% 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 tool's function: querying all matching child elements within an element using a WXSS selector. It distinguishes itself from sibling tools like element_query by explicitly saying 'all' and describing the return of an array of element_id handles.

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 usage is implied by the 'query all' semantics and the description mentions the tool operates on child elements, but it does not explicitly state when to use this tool versus alternatives like element_query or xpath variants. There is no exclusion or alternative naming, so the guidance remains implicit.

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