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

Annotations already establish readOnlyHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: result shape (id, title, snippet, relevance, resource type), the 30-result cap, and the fields='*' inline-expansion behavior. It omits pagination behavior, which is minor given the hard cap.

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?

Three tight sentences with the purpose front-loaded and no filler. The trailing 'Kayako: GET /api/v1/search.json' mapping is useful for endpoint-aware agents but is the least essential element.

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 no output schema, the description usefully names the returned fields and the fields='*' expansion, and shares the result cap. Combined with a fully documented schema and a read-only annotation, an agent has enough to call this correctly; only pagination and query-language specifics remain unstated.

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 all four parameters are already documented in the schema, including the fields='*' example and the 1-30 limit range. The description largely restates those facts (max 30 results, fields='*' inline), adding no syntax or format detail beyond the schema. Baseline 3 applies.

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 and resource set: unified search across conversations (cases), users and organizations. Scoping to those three resource kinds implicitly separates it from kayako_search_help_center and the various list_* tools, though no sibling is named explicitly.

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?

Usage is only implied — an agent can infer this is the entry point when it lacks an id and needs to locate cases/users/orgs before calling kayako_get_case or kayako_get_user. There is no explicit when-to-use statement and no guidance on when to prefer kayako_list_cases or kayako_search_help_center instead.

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