get_infrastructure_hosts

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

No annotations provided, so the description carries full burden. It only states 'get', implying read-only, but lacks details on rate limits, pagination, scope (e.g., all hosts? filtered?), or behavior of the 'hours' parameter. Agent is left uninformed about important constraints.

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, front-loaded sentence with no wasted words. However, it is extremely brief, sacrificing completeness for conciseness. Could include more detail without becoming verbose.

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 only one parameter and no output schema, the description should still hint at return format or behavior. It omits any mention of what the response contains (e.g., list of hosts, metrics per host), leaving the agent guessing. Incomplete for a tool that likely returns complex data.

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 provides 100% coverage with a description for the single 'hours' parameter. The description adds no extra meaning, so baseline score of 3 is appropriate. No additional context about how 'hours' affects results.

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 'Get infrastructure hosts and their metrics', specifying verb and resource. However, it does not differentiate from sibling tools like entity_search or get_entity which also retrieve infrastructure hosts, missing a chance to clarify uniqueness.

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?

No guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or when not to use it. For a tool that may overlap with entity search or specific entity retrieval, this is a significant gap.

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