hh_fetch_all

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

The description adds substantial behavior beyond the annotations: it discloses auto-pagination handling of offset/last_id/cursor/page/WB lastChangeDate, that array path is resolved automatically, cursor fields are managed, and that max_items is a hard cap with a truncated flag. This is exactly the kind of behavioral disclosure annotations don't cover.

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?

It front-loads the core purpose in two sentences, then provides a compact bullet-style Args list. Every sentence adds operational value, with defaults in-line and unusual mechanics (array path, cursor handling) explicitly mentioned. 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 tool's many parameters, zero schema descriptions, and generic pagination role, the description is impressively complete. It explains expected result format, pagination style compatibility, path extraction, cursor management, and safe limits. The output schema presumably covers field details, so nothing essential is missing.

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%, so the description carries all parameter semantics. It explains operation_id, query/body/path_values as base parameters, cursor fields being managed, items_path as the override path, limit as the page size, and max_items as the context cap. This fully compensates for the sparse 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 opens with 'Auto-paginate a read endpoint and return every row in one response', which is a specific verb+resource statement. It also enumerates the pagination styles it supports and returns envelope details, and the contrast with sibling tools like hh_call_method makes its role as a fetch-all helper clear.

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 clearly says when to use it: when you need every row from a read endpoint. It also warns about the max_items cap, which is useful guidance. However, it does not explicitly name alternatives such as a single-page call method, so there is no explicit when-not-to-use detail.

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