list_zerotrust_hostname_routes

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List' implies a read-only collection operation, but nothing is said about pagination, result ordering, limits, or what a hostname route entry looks like. The description adds no behavioral context beyond what the verb 'List' already conveys.

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 only five words and is efficiently front-loaded, but it is minimal to the point of restating the tool name. It earns its place structurally but does no additional work. There is zero waste, yet also zero added informational value.

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, no annotations, and only a one-sentence description, the definition leaves the agent without context on pagination, result shape, or the distinction between hostname routes and teamnet routes. The single account_id parameter is documented, but the operation's return behavior is entirely unspecified. For a list tool with sibling ambiguity, this is incomplete.

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% — account_id is documented as 'The account ID' in the schema, so the structural burden is already met. The tool description adds no additional semantic meaning about the parameter, so the baseline of 3 applies. Some value would have been added by explaining the relationship between account_id and the hostname route scope, but that is absent.

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 states a specific verb ('List') and resource ('Zero Trust hostname routes'), so an agent can tell it is a read/collection operation. It does not explicitly differentiate itself from siblings like get_zerotrust_hostname_route or list_teamnet_routes, but the singular/plural naming convention and distinct resource term provide implicit separation. It is clear but essentially restates the tool name, so it falls short of a 5.

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 guidance about when to choose this tool over alternatives such as get_zerotrust_hostname_route, list_teamnet_routes, or list_magic_transit_routes. No conditions, prerequisites, or exclusions are mentioned. An agent must infer the use case entirely from the name and sibling list.

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