Disable lineup location

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is largely covered. The description adds the endpoint it hits but does not say whether the change is reversible, what state the device ends up in, or whether auth/lockkey is required for this mutation.

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 short sentence with the action front-loaded and the endpoint appended as supporting detail. No filler, though the literal path markup is slightly noisy for an agent-facing description.

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 zero-parameter toggle with no output schema and annotations covering safety, the description is nearly sufficient. The main omission is a pointer to the inverse operation for re-enabling, which the sibling name largely implies.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The noted endpoint path is extra context rather than parameter guidance.

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?

States a specific verb (Disable) and resource (lineup-server connection) with the underlying endpoint path, so the action is unambiguous. The inverse sibling hdhomerun_set_lineup_location is not named, but the paired naming makes the distinction clear enough.

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 is only implied by the name: use it to turn off the lineup location rather than to configure one. There is no explicit statement about when to prefer this over hdhomerun_set_lineup_location or what prerequisites (device reachability, auth) apply.

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