search_hosts_by_location

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

The description discloses the default limit of 10 results via 'Returns max 10 results by default.' No annotations are provided, so the description carries full burden. It lacks details on error cases, authentication needs, or output format, but is adequate for a read-only search.

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 concise with two sentences and a 'CONTEXT OPTIMIZATION' line. It front-loads the purpose and is free of unnecessary details, though the formatting is slightly informal.

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 search tool with 2 parameters and no output schema, the description covers the core behavior and a key default. However, it omits pagination details and does not compare with sibling tools, leaving some gaps for an agent.

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 0%, so the description must compensate. It provides examples for the location parameter and hints at per_page via the default limit. However, it does not fully describe the parameters or their expected values.

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 'Search hosts by location' with examples like 'SYD03', indicating the function. It distinguishes from sibling tools (e.g., search_hosts_by_environment) by specifying the location parameter, but does not explicitly contrast them.

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 like search_hosts_by_environment or search_hosts_by_fact. The tip 'Use specific location codes for best results' is helpful but does not address selection criteria.

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