GetAllInventoryHosts

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

No annotations are provided, so the description carries full burden. It states this is a 'Get' operation, implying read-only behavior, but doesn't disclose any behavioral traits like authentication requirements, rate limits, pagination, or what 'all servers' entails (e.g., scope, format, or potential performance impact). The description is too minimal to provide meaningful 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?

The description is a single, clear sentence with no wasted words. It's appropriately front-loaded with the core purpose, making it efficient for an agent to parse.

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 the complexity (1 parameter with nested objects, no output schema, no annotations), the description is insufficient. It doesn't explain the parameter, return values, or behavioral expectations. For a tool that likely returns a list of inventory hosts, more context is needed to use it effectively.

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 input schema has 1 parameter ('body') with 0% description coverage in the schema. The tool description provides no information about parameters, leaving the agent with no guidance on what 'body' should contain or if it's even required. This fails to compensate for the lack of schema documentation.

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 action ('Get all') and resource ('servers available for inventory browsing'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'GetAllInventoryVmwareHosts' or 'GetAllInventoryPGs', which appear to serve similar inventory-related purposes.

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 provides no guidance on when to use this tool versus alternatives. With many sibling tools that seem related to inventory (e.g., 'GetAllInventoryVmwareHosts', 'GetAllInventoryPGs', 'GetInventoryObjects'), there's no indication of how this tool differs or when it's the appropriate choice.

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