List Logitech Sync network inventory

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

Beyond annotations (readOnly, idempotent, not destructive), description adds that missing fields remain absent (avoids hallucination), does not scan or change config, and returns bounded entries with metadata. Provides valuable behavioral context.

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?

Concise at 5 sentences covering purpose, search capability, behavioral note, actions not taken, and return type. No unnecessary words, but could be more structured.

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?

Given 10 parameters, output schema, and sibling tools, description covers main search and filter capability, return types, and key behavioral notes. Omits mention of desk/room/licensed filters, but these are in schema. Adequately complete for an inventory listing 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 has 100% coverage with detailed descriptions. Description adds a high-level summary of search and filter (query, interface_mode) but does not add new semantics. Baseline of 3 appropriate due to full schema coverage.

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?

Clearly states it lists network inventory with specific fields (IPs, MACs, hostnames, interfaces). Distinguishes from siblings by focusing on network rather than general inventory. Includes what it does and does not do.

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?

Describes search and filter options but does not explicitly compare to sibling 'logitech_sync_search_inventory'. Lacks when-to-use and when-not-to-use advice. Provides some context (does not scan network), but no alternative tool names.

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