inventory__get_host_system_profile

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

Annotations already declare readOnlyHint=true, but the description adds value by warning about large response sizes that could overload context, which is beyond the annotation's capability.

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 short paragraph that is front-loaded with the main purpose. It could be slightly more concise, but it efficiently conveys the scope without excessive verbosity.

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?

An output schema exists, so return values are documented elsewhere. The description provides a useful summary of what is returned (e.g., CPU, memory, BIOS), which is sufficient for understanding the tool's capability.

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 description coverage is 100%, so the schema already documents the parameter thoroughly. The description adds no additional meaning about the parameter itself, listing only the return fields.

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 it 'Get detailed system profile information for specific hosts' and enumerates what is included (CPU, memory, network, etc.), distinguishing it from sibling tools like inventory__get_host_details which likely provide basic info.

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 does not explicitly state when to use vs. alternatives, but the parameter description in the schema provides crucial guidance: 'ALWAYS supply one or two UUIDs at a time! Expect really large responses which will overload your context.' This helps the agent use the tool appropriately.

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