get_custom_hostname

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get details' implies a read operation but does not disclose what happens if the custom hostname is not found, whether the response is paginated, what fields are returned, or whether special permissions are required. This is minimal transparency for a GET-style tool.

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 single, front-loaded sentence with no filler or repetition. Every word contributes to identifying the operation and resource.

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 two-parameter retrieval tool, the description is adequate but not complete. It does not explain how this tool relates to list_custom_hostnames, what constitutes 'details', or what the response shape looks like, and there is no output schema to compensate. The parameter validation is entirely delegated to the schema, which is acceptable but leaves usage context missing.

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?

The input schema already provides full descriptions for both parameters (zone_id and custom_hostname_id), so schema coverage is 100%. The description adds no parameter-specific meaning beyond what the schema states, which meets the baseline for high schema coverage.

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 a specific action ('Get details') and resource ('custom hostname'), and the word 'specific' signals that this is a single-resource retrieval rather than a list operation. It implicitly distinguishes itself from the sibling tool list_custom_hostnames, though it does not explicitly name the alternative.

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 gives no guidance on when to use this tool versus alternatives such as list_custom_hostnames. There is no mention of prerequisites like obtaining the custom_hostname_id first, nor any exclusion criteria. This leaves the agent to infer context from the parameter names alone.

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