inventory_scan

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

No annotations provided; description only states a non-destructive action ('collect') but does not disclose behavioral traits such as permissions, side effects, or output details. Minimal transparency.

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?

Single sentence with clear verb and resource, listing what is included. No wasted words, front-loaded.

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?

Description explains purpose and scope, but lacks output format or return behavior. With no output schema, some guidance on result structure would enhance completeness for a scanning 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% with one parameter well-described in schema. Description adds no additional meaning beyond schema, but baseline is 3 due to high 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?

Description clearly states it collects server inventory/topology and lists specific components (system status, Docker containers, app ports, system ports). Verb 'collect' with specific resource, differentiating it from sibling tools like docker_list or open_ports.

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?

Implied usage as a comprehensive scan, but no explicit when-to-use or when-not-to-use compared to alternatives like network_scan or system_status. Provides optional server param context but lacks usage boundaries.

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