superops_navigate

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explains that the tool returns tool names and descriptions, and it clarifies the non-gating nature ('All tools are callable at any time — this is a help/discovery aid, not a prerequisite'). This is meaningful behavioral context beyond the schema.

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 sentences, each earning its place: the first states purpose and output, the second removes a common misconception about prerequisite behavior. It is front-loaded and contains no filler.

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 single-parameter discovery tool with no output schema, the description covers purpose, return content, and a key behavioral caveat. It does not detail the exact response structure, but that is not necessary for an agent to invoke and interpret a help/discovery 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 coverage is 100% and the single domain parameter has detailed descriptions for each enum value, so the schema fully explains parameter semantics. The tool description itself adds no additional parameter meaning, which is appropriate given the rich schema.

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 a specific verb ('Discover'), a resource ('available SuperOps.ai tools'), and a scope ('by domain'). It also explicitly states what is returned ('tool names and descriptions'), making it clearly distinct from the operational sibling tools like superops_tickets_get or superops_clients_list.

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 positions this as a help/discovery aid, making its intended use clear. It also explicitly states it is not a prerequisite for other tools, which prevents an agent from incorrectly treating navigation as a required step. It does not explicitly list alternatives, but the siblings are operationally different.

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