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

No annotations are provided, so the description carries the disclosure burden. 'Search' implies a read-only operation, but the description does not state that it returns a list of matches, lacks pagination info, or clarify that it does not modify data. The behavior is minimally transparent but not fully explicit.

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 that efficiently conveys the tool's scope with no redundant phrases. Every word contributes to understanding the tool's purpose.

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 is relatively simple, but the description omits guidance on when to use it versus sibling get_* tools and does not describe the return format or any search limitations. Given no annotations and no output schema, the description should provide more behavioral and usage context to be fully complete.

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 input schema has 100% parameter description coverage, so the baseline is 3. The description adds semantic value by mapping the enum value 'posts' to 'blog posts', clarifying a potentially ambiguous term. It also reinforces the content-type scope via its listed examples.

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 uses the specific verb 'search' and identifies the resource as 'all Ski Limone content', listing concrete categories (hotels, restaurants, blog posts) that distinguish it from the sibling get_* detail tools. This clearly states what the tool does and sets it apart.

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 a general search use case but does not explicitly say when to choose it over the sibling get_* tools, nor does it mention any exclusions or prerequisites. The context signals show sibling tools for specific details, so the intended usage is inferred but not articulated.

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