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

The phrase 'before running it' clarifies that the tool recommends rather than executes, which is meaningful behavioral context. Annotations already indicate readOnly, idempotent, and non-destructive behavior, so the description supplements rather than contradicts them.

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?

Two concise sentences: the first states the core function and the second gives the triggering usage. There is no filler or repetitive phrasing.

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, single-parameter, read-only recommendation tool, the description is complete. The output schema covers return details, annotations cover safety, and the description provides purpose and usage context.

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 the prompt parameter already documented as the task/request to match against installed Contexts and Workflows. The tool description adds little beyond that, so it meets the baseline without significantly enriching parameter meaning.

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 states a specific action ('Recommend') and a specific resource ('best Oi Context or Workflow for a prompt'). It is clear about what the tool does, though it does not explicitly distinguish itself from related search/use siblings such as oi.contexts.search or oi.workflows.use.

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 a direct when-to-use condition: when the user asks 'oi recommend' or wants help choosing the most suitable reusable setup. It does not list when-not-to-use or explicitly name alternatives, but the intended context is clear.

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