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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the useful scoping fact that the corpus is Offline Protocol product workflows, but says nothing about result count, ranking, or pagination.

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 front-loaded sentence with the resource named first and the qualifier second; no filler. The embedded example list is the only slight lengthening, and it earns its place by clarifying the domain.

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 tool with full annotation coverage and no output schema, the description covers what it searches and over what domain. The only gap an agent might want is how results are shaped or ranked, which is minor here.

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?

One parameter with 100% schema description coverage, so the baseline is 3. The description adds semantic intent for the query (keywords describing what you want to build), which is mildly useful, but adds no format, length, or phrasing guidance beyond the schema's "Search keywords" (max 200).

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?

States a specific verb (search) and resource (Offline Protocol product workflows) with concrete examples of the workflow domain (local handoff, nearby chat, backend delivery, OfflineID sign-in). The resource noun distinguishes it from the search_packages/search_skills/search_examples siblings, but it never names an alternative so the differentiation is implicit rather than explicit.

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?

"by keywords describing what you want to build" implies the discovery use case, but there is no explicit when-to-use statement, no contrast with get_workflow or list_workflows, and no note that this is the right entry when the workflow ID is unknown. Usage is implied only.

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