Search Bubbles

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

The readOnlyHint annotation already communicates a safe read operation. The description adds the 'current and historical' scope but does not disclose other behavioral aspects such as pagination or filtering behavior. This is acceptable given the annotation, but not rich.

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, front-loaded sentence with no filler. It efficiently conveys the core purpose without unnecessary detail.

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?

The tool has 4 parameters and no output schema, yet the description provides minimal context. It lacks details about return format, filtering by platform/timeframe, or what constitutes a 'Bubble'. The description is too skeletal for a tool with these options.

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?

With 0% schema description coverage, the description should compensate, but it only partially hints at the 'query' parameter by listing example search subjects. It does not explain the limit, platforms, or timeframe parameters, leaving significant ambiguity.

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 searches for Bubbles about specified topics, with a specific verb and resource. It indicates scope (current and historical) but does not explicitly differentiate from sibling tools like get_bubbles or get_bubble_details.

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 keyword-based searching but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. The use case is inferred from the listed search subjects.

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