omni_knowledge

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

With no annotations, the description carries the burden of behavioral disclosure. It does convey that this is a read-only fetch of static content, which is useful. However, it does not mention what the response looks like, whether content is large or paginated, or what happens when topic=all is requested.

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 a single sentence that front-loads the core action and resource, then lists topics efficiently. There is no filler or redundancy, and every clause adds useful context.

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 static knowledge-base lookup, the description covers the main topics and communicates read-only behavior. However, the absence of an output schema and annotations, plus missing enum values and no return-format details, leaves some gaps that an agent may need to discover by calling the tool.

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 50%: pitfallId is documented in the schema but topic is not. The description adds meaning to several enum topics ('recipe shapes', 'staging paths', 'endpoint catalog') beyond the bare labels, but it omits mapdev, repos, and all, and does not explain the pitfallId parameter or its relationship to topic=pitfalls.

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 ('Fetch') and a specific resource ('the static OmniMod knowledge base'), then enumerates the main topic areas it covers. This makes the tool's purpose clear, though it does not explicitly differentiate it from sibling documentation tools like omni_help or omni_map_docs.

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 given for when to use this tool versus alternatives like omni_help, omni_map_docs, or omni_map_guide. The word 'static' implies it is for fixed reference content rather than live state, but there are no explicit conditions, exclusions, or routing hints.

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