Ruleset

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention that install/remove/bind mutate state, what happens with a ruleset-free novel beyond not using this tool, or any failure/return behavior. The description only provides usage context, not operational transparency.

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 tightly structured sentences with purpose front-loaded and a clear Use/Do NOT use parallel. Every sentence earns its place and there is no filler, though the noun 'lookup' is slightly awkward.

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 tool with six actions, twelve parameters, no annotations, and no output schema, this description is too thin. It entirely omits the 'roll' action and gives no indication of return values, state-changing behavior, or per-action semantics. The schema helps with parameters but cannot compensate for missing action coverage.

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?

The schema covers all 12 parameters with descriptions, so the baseline is 3. The description adds minimal context about searching a bound ruleset's index, but it does not provide meaningful parameter-level meaning beyond what the schema already supplies.

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 the tool manages ruleset packages and explicitly lists search, install, remove, list, and bind as use cases, while also distinguishing it from command and session in the negative case. However, it omits the 'roll' action from the action enum and uses the slightly vague phrase 'lookup', so it is not fully precise.

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 gives clear 'Use when' and 'Do NOT use when' guidance, including specific alternatives (command action: suggest, session action: health). It is explicit for the listed cases, but incomplete because 'roll' is not mentioned as an eligible use, leaving a gap in routing.

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