bubble_search_all

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

Annotations already mark it as read-only, idempotent, and non-destructive. The description adds valuable behavior: auto-pagination, combined results, and a capped flag when the limit is reached. This goes beyond annotations but doesn't fully cover edge cases like error handling or empty results.

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 two sentences, front-loaded with the primary action, and then reports the return behavior. Every word contributes meaning, with no fluff or repetition of schema details.

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 moderate complexity and no output schema, the description adequately covers the core pagination behavior and the capped flag. It doesn't explain how constraints/sort affect pagination, but these are documented in the input schema. Overall, it provides sufficient context for correct 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?

Schema coverage is 100%, so the parameters are fully documented in the schema. The description only loosely references 'configurable max' without adding syntax details, which the schema already provides. Thus it meets the baseline without further enrichment.

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 states a specific verb ('auto-paginates'), the resource ('all records of a Bubble data type'), and a key constraint ('up to a configurable max'). This clearly distinguishes it from sibling tools like bubble_search and bubble_get, which likely operate on single pages or records.

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 indicates this tool is for retrieving all records of a data type, implying use when a full sweep is needed. However, it does not explicitly state when to avoid this tool or mention alternatives such as bubble_search for manual pagination, so it falls short of a 5.

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