get-host-totals

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds that it returns totals and can be filtered by 'from' time. However, it does not disclose output format, behavior with no hosts, or error conditions. Some behavioral context is added but not in depth.

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?

One sentence, nine words, no redundancy. Information is front-loaded. Could be slightly more structured but is appropriately concise for a simple tool.

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?

For a simple tool with one optional parameter and no output schema, the description is adequate but incomplete. It does not specify the return format (e.g., single number or object), which the agent would need to interpret results. With no output schema, the description should clarify output structure.

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 the 'from' parameter described. The description mentions time-based totals but does not add meaning beyond the schema's parameter description. Baseline of 3 applies.

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 the function: 'Get total number of active and up hosts'. It uses a specific verb and resource, distinguishing it from sibling tools like 'list-hosts' which likely return detailed host lists.

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?

Usage context is implied (aggregate vs. list), but no explicit when-to-use or when-not-to-use guidance is provided. The description does not contrast with sibling tools like 'list-hosts' or 'get-metrics'.

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