oracle_linux_package_list

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

Description implies a read-only operation (listing installed packages) but does not explicitly state safety or non-destructiveness. With no annotations, the description carries full burden; while the behavior is clear, it could be more explicit about being non-modifying.

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 that efficiently conveys the tool's purpose and output. No redundant or extraneous information.

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?

For a simple list tool with two parameters and no output schema, the description sufficiently communicates the scope (installed packages) and output fields. It is complete given the tool's straightforward nature and the existence of sibling tools that cover other operations.

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% and both parameters have descriptions in the schema ('target' and 'filter'). The description adds no additional parameter-level meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 'List installed RPM packages' using a specific verb and resource, and specifies the output fields (version, release, arch, install date). It distinguishes itself from sibling tools like install, remove, search, and update by focusing on listing currently 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 is provided on when to use this tool versus alternatives such as oracle_linux_package_search. The description only states what it does without offering context on prerequisites, scope, or exclusions.

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