okf_search_tool

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

With no annotations, the description carries the behavioral disclosure burden. It usefully reveals that hits from other bundles include a `bundle` field when all_bundles is set, but it does not disclose ordering, pagination semantics of limit, or behavior when both bundle and all_bundles are supplied.

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 two tight sentences with the main action front-loaded and no filler. Every sentence adds information about scope or result behavior.

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?

Given no annotations and zero parameter descriptions, the description is only moderately complete. It explains the all-bundles mode and the bundle field on hits, but leaves ambiguous how to address a specific bundle and how limit applies; the output schema does help cover return-value expectations.

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 0%, so the description was expected to compensate. It only clarifies all_bundles and vaguely implies the bundle parameter via 'one or all loaded bundles'; term and limit receive no semantic explanation beyond their schema types.

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 states a specific action ('Search') on a clear resource ('one or all loaded bundles') and explains the all_bundles mode. It is clear but does not explicitly differentiate this tool from the sibling search_chunks, so it falls just short of a 5.

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?

It gives concrete guidance for using all_bundles=True to cover every registered bundle, and implies the alternative of searching a single bundle. However, it does not mention when to prefer this tool over sibling search tools such as search_chunks, nor any exclusions.

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