Argus demonstrates solid naming conventions (verb_noun pattern: argus_overview, netgear_nighthawk_radio_set) and comprehensive descriptions (avg 120 chars, all tools documented). However, schema quality is inconsistent: 11 tools have empty input schemas ({}), forcing a hard cap at 0 for schema scoring on those tools. Write-path tools (netgear_nighthawk_radio_set, netgear_nighthawk_ssid_set, devolo_dlan_ssid_set) properly declare confirm/dryRun parameters with descriptions, but lack explicit output schema documentation. Error handling is present (ArgusError class, recovery guidance in descriptions like 'may take a few seconds'), but not all tools document what errors they can raise or how to recover. Composition is strong: tools chain well (argus_capabilities feeds into argus_invoke), and the escape-hatch pattern (argus_invoke) is well-designed. Security is good: no credentials in parameters, confirm gates on destructive ops. Overall: above-average naming and descriptions, but empty schemas on 61% of tools and missing output documentation drag the score down.

• Add explicit input schemas to all 11 read-only tools. Even if parameters are optional, declare them as empty objects with type 'object' and properties: {}. Better: add optional limit/offset for list tools (argus_overview, argus_capabilities, netgear_nighthawk_clients_list, devolo_dlan_clients_list).
• Document output schemas for all tools. Use JSON Schema to describe the structure of returned objects. E.g., argus_overview should return {site: string, devices: [{id: string, status: string, ...}]}. This enables LLMs to chain calls and extract IDs.
• Add pagination to discovery tools. argus_overview and argus_capabilities should accept limit (default 20, max 100) and offset/cursor parameters. Return total_count or next_cursor so agents can iterate over large device lists.
• Enhance error descriptions in write-path tools. For netgear_nighthawk_radio_set, add: 'Returns error if device is offline, band does not exist, or confirm=false. Retry with confirm=true and dryRun=false to apply changes.'
• Add tool annotations (readOnlyHint, destructiveHint, idempotentHint) to the MCP server registration. Mark read-only tools with readOnlyHint=true, write tools with destructiveHint=true, and idempotent tools with idempotentHint=true. This helps clients optimize caching and retry logic.