superops_navigate

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

With no annotations, the description must carry the burden of behavioral disclosure. It does state the output ('Returns tool names and descriptions') and positions the tool as a 'help/discovery aid,' which implies no side effects. However, it does not explicitly state that the tool is read-only or has no mutating effects, which is important when no annotations are present. This is adequate but not rich.

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 concise sentences that front-load the core purpose ('Discover available SuperOps.ai tools by domain') followed by a clarifier about the tool's non-prerequisite nature. Every word earns its place; no redundant or vague content.

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 tool with one parameter, the description fully covers what the tool does, what it returns, and its optional status. With no output schema, the description appropriately states the return format ('tool names and descriptions'). It is complete for the tool's complexity, though it could specify the exact structure of the returned data (e.g., list vs. object), but this is minor.

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%: the single 'domain' parameter includes a detailed enum with descriptions for each option (clients, tickets, assets, technicians, custom). The tool description merely says 'by domain,' which adds no additional meaning beyond the schema. Baseline for high coverage is 3.

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 clearly states the tool's function: 'Discover available SuperOps.ai tools by domain' and specifies the return value ('Returns tool names and descriptions for the selected domain'). It uses a specific verb ('Discover') and resource ('SuperOps.ai tools'), and distinguishes itself from siblings by positioning as a discovery aid rather than an operational tool.

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 explicitly states the tool is a 'help/discovery aid' and clarifies that 'All tools are callable at any time — this is a help/discovery aid, not a prerequisite.' This effectively tells the agent when to use it (to discover tools) and when not to (it is not a required precursor to other calls). It does not name alternative tools, but given its discovery purpose, the context is clear.

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