omni_help

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully reveals that the tool returns the running device's own endpoint list and is self-describing, but it does not describe the output format, potential size, or whether the list includes sibling tools explicitly.

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 short and conveys the essential information in two sentences. The first sentence is slightly awkward and could be more direct, but it contains no waste and the usage guidance is front-loaded at the end.

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 zero-parameter introspection tool with no output schema or annotations, the description provides adequate context: what the tool is, what it returns, and when to use it. It could mention how to interpret the returned catalog, but the core information needed to invoke it correctly is present.

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 tool has zero parameters and 100% schema description coverage, so the schema already fully documents the input surface. Per baseline for parameterless tools, the description does not need to add parameter semantics, and it doesn't.

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 identifies the tool as a 'self-describing endpoint catalog' and explains that the engine returns its own list. It conveys the resource and action well enough to distinguish it from sibling tools, though the phrasing is somewhat jargon-heavy and lacks a direct verb like '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 explicitly states when to use it: 'Use this to discover platform-specific additions.' This gives clear context for the primary use case, but it does not mention exclusions or contrast with sibling tools that might also relate to platform discovery.

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