get_inventory

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

Annotations declare readOnlyHint/openWorldHint, but the description adds genuinely non-obvious behavior: it surfaces the effective privilege of the logging-in BMC account (account.role, account.can_control) and emits a warning when a target lacking dangerous classes uses an account that could power it off. That proactive safety behavior is not derivable from the annotations or schema.

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 entire description is a single run-on sentence that mixes the core purpose, three distinct return fields, and a conditional safety warning. It is not front-loaded; the important warning behavior is buried at the end, making it easy to miss.

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?

With no output schema, the description carries the return-shape burden and does so reasonably by enumerating the main fields. A read-only tool with one well-documented parameter needs little more, though it omits any mention of result scope or how multiple targets are aggregated.

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% and the single 'targets' parameter is fully documented with 'all' and 'tag:<tag>' syntax. The description only restates 'one or many servers' and adds no format or default detail beyond the schema, so the baseline 3 is appropriate.

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 names the specific resource and enumerates the fields returned (vendor, model, serial, BIOS/BMC firmware, CPU/memory, power state, account role), so an agent knows exactly what it retrieves. It does not, however, distinguish itself from overlapping siblings like get_firmware_inventory or get_power_state, leaving scope boundaries ambiguous.

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?

There is no explicit statement of when to choose this tool over alternatives, despite several siblings (get_firmware_inventory, get_power_state, get_health) that clearly overlap. Usage is only implied by the field list.

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