oracle_linux_package_search

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

No annotations provided; description must fully disclose behavior. Description is minimal and does not mention network requirements, side effects, or response format. Agent cannot infer if this tool modifies state or requires special permissions.

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?

Single sentence, no fluff, directly states the action. Every word 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?

Lacks output schema, no annotations, and description does not cover what the search returns, handling of no results, or error conditions. For a search tool in a package management context, this is insufficient for an agent to use correctly.

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% with basic descriptions for both parameters ('Search query' and 'Target name from ~/.dbx/targets/'). Tool description adds minimal value by mentioning 'configured yum/dnf repositories', but does not elaborate on format or constraints beyond schema.

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?

Description clearly states the tool performs a search for available packages in configured yum/dnf repositories. It uses specific verb 'search' and resource 'available packages', but does not explicitly differentiate from sibling tool 'oracle_linux_package_list' which might list installed packages.

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?

No guidance on when to use this tool versus alternatives like 'oracle_linux_package_list' or 'oracle_linux_package_install'. Does not mention prerequisites or when not to use.

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