Discover plugin packages

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does convey that discovery spans multiple forest locations, but it does not state what the tool returns, whether it is read-only, or how cwd/workspace affect traversal. This leaves meaningful behavioral gaps.

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?

A single front-loaded sentence conveys the purpose and scope, with a parenthetical of concrete path patterns that earns its place. There is no filler or repetition of schema details.

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 reasonably complete for a simple two-optional-parameter discovery tool, but there is no output schema and no mention of the return shape or how results are organized. An agent would still be uncertain about what the tool actually yields.

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%, so the schema already documents cwd and workspace clearly. The description adds helpful forest-scope context but does not materially clarify parameter semantics beyond what the schema provides, so the baseline 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?

The description uses a specific verb ('Discover') and a concrete resource ('plugin packages'), and defines the exact scope with the RHDH forest levels and examples. This distinguishes it clearly from sibling tools like list_layers or inventory_tests, which address different artifacts.

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 the tool is for enumerating plugin packages across all defined RHDH forest levels, but it does not explicitly state when to use this tool versus alternatives or mention any exclusions. Context is present, but selection guidance is left to inference.

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