radarr_get_config_host_by_id

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

Annotations already declare readOnlyHint: true, so the safety profile is known. The description adds minimal context (single host, by id) but does not disclose behaviors like what happens if the id is not found or any permission requirements beyond the read-only hint.

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 concise sentence, front-loaded with the action. It has no wasted words, but it is somewhat under-specified for a tool with no parameter descriptions, so it earns a 4 rather than a 5.

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?

The tool is simple with one parameter, an output schema exists, and readOnlyHint is present. The description is minimally sufficient for basic invocation but lacks usage guidance and parameter semantics, making it just adequate for an agent to select and use correctly in many cases.

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 schema has one required integer parameter 'id' with 0% description coverage. The description's 'by id' does indicate that id is the host identifier, but it does not explain the id's format, how to obtain it, or provide examples. This is minimal compensation for zero 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 'Fetch a single host by id' clearly states a verb (fetch), resource (host), and scope (single, by id). This is distinct from a tool like radarr_get_config_host which likely lists or fetches the global host config, though the description 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?

No guidance is provided on when to use this tool versus siblings like radarr_get_config_host or radarr_get_config_host (without by_id). The name implies usage when you have a specific id, but the description does not state this or mention alternatives.

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