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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact: the search spans every group, with no per-group scoping. It says nothing about pagination, result limits, or case sensitivity, which are the remaining unknowns for a search operation.

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?

A single sentence that front-loads the action and the scope, with no filler or repetition of the title. Every clause ("saved tabs", "every group", "title or URL text") carries information.

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?

For a one-parameter read-only search with annotations covering safety, the description is close to sufficient. What an agent still cannot determine is the result shape, ordering, or whether results are capped, and there is no output schema to fill that gap.

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 has 0% description coverage for the single required "query" parameter, so the description must compensate. It does partially, clarifying that the query matches against title or URL text, but it gives no syntax, matching mode, or length constraints beyond the schema's minLength.

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 names a specific verb ("Search") and resource ("saved tabs") and states the scope ("in every group") plus the match fields ("title or URL text"). This distinguishes it from the sibling listing tools (list_groups, list_projects, get_group), though it never explicitly contrasts itself with them.

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?

There is no when-to-use guidance, no stated prerequisites, and no mention of alternatives such as browsing a specific group instead. The only implied usage is that an agent calls it when it wants to find a tab by text, which an agent could already infer from the name.

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