trmnl_add_fleet_device

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

Annotations already declare non-read-only, non-idempotent, open-world behavior, and the description adds real constraints beyond them: the device joins as a mirror (not master), and a device may belong to only one fleet. The closing line about remote state and authorized scope is generic boilerplate rather than new information.

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?

Short and front-loaded: the core action comes first, followed by role and constraint notes. The endpoint URL and the boilerplate 'Changes remote state...' sentence add little for the reader and could be trimmed.

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 mutation tool with nested body objects and no output schema, the description covers the what and the fleet-membership rule but leaves device_id semantics, failure modes (e.g., device already in another fleet) and return content unexplained. Adequate but with clear gaps.

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 only 33% and the description never mentions any parameter. The endpoint string hints at installation_id in the path, but body.device_id (a required integer) and the optional profile parameter receive no clarification in either place.

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 and resource ('Add a device to a fleet as a mirror') and clarifies the resulting role of the device. It does not explicitly differentiate itself from nearby siblings such as trmnl_push_fleet_device or trmnl_remove_fleet_device, but the membership semantics are clear.

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?

Gives a concrete precondition ('A device can be in one fleet only') and points to the promotion path via setFleetMaster, which tells the agent this is the joining step rather than the promotion step. No explicit when-not guidance or error cases are stated.

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