bubble_search

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

Annotations already cover readOnly, idempotent, and non-destructive behavior. The description adds minor behavioral context (optional constraints, sorting, pagination) but does not disclose additional traits like return format or cursor semantics. With annotations present, this is adequate but not enriched beyond structured data.

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, concise sentence that front-loads the core purpose and optional features. There is no wasted text or 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?

With a well-documented schema and safety annotations, the description is largely complete. It does not explain the return value (e.g., list of objects, count), but for a simple search tool this is a minor gap, especially given no output schema exists.

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 100%, so the schema fully documents all parameters. The description's mention of constraints, sorting, and pagination aligns with the schema but adds no extra meaning beyond what is already provided.

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 action (search), the resource (Bubble.io data objects of a given type), and the key capabilities (optional constraints, sorting, pagination). It distinguishes itself from siblings like bubble_get (single object) and bubble_search_all (all types) by specifying 'of a given type'.

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 implies usage for a specific data type but does not explicitly state when to use this tool vs alternatives. It lacks explicit when-to-use/when-not-to-use guidance or alternative recommendations, though the scoping to a given type is a clear contextual clue.

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