search_kamelets

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

With no annotations, the description must disclose behavioral traits. It only states the search fields (name, title, description) but omits details like case sensitivity, partial matching, pagination, or any potential side effects. The tool's read-only nature is implied but not explicitly stated.

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 extraneous words. Every word is meaningful and earns its place.

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 description is minimal for a search tool. It does not specify return format (list, object, count), result limits, or pagination. Given the complexity of search tools and lack of output schema, this is insufficient for an agent to fully understand the behavior.

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 coverage is 100%, so the schema already defines 'query' as a string. The description adds meaning by clarifying that the search applies to name, title, or description, which is useful beyond the schema's 'Search query' label. However, this is baseline value given high coverage.

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 Apache Camel Kamelets by name, title, or description. It uses a specific verb 'Search' and resource 'Kamelets', distinguishing it from siblings like 'get_kamelet_details' (which retrieves details) and 'search_components' (which searches other entities).

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 does not provide any guidance on when to use this tool versus alternatives, such as 'get_kamelet_details' for specific kamelets or 'search_components' for other components. No inclusion or exclusion criteria are given.

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