trmnl_get_fleet

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

Annotations already declare this is read-only, idempotent, open-world, and non-destructive, so the description does not need to restate safety. It adds useful behavioral context by enumerating what the fleet read exposes, including master device, mirror push needs, inherited settings, and overdue alert status.

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 short and front-loaded, with the main purpose and returned content stated before the sibling reference and endpoint. The phrasing is slightly awkward due to the missing punctuation after "Read a fleet," but there is little wasted text.

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 read-only fleet summary tool with annotations covering safety and no output schema, the description provides enough return-value context to understand what will be fetched. The main remaining gap is the optional profile parameter, which is left to the schema.

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 coverage is only 50%, and the description only reinforces the installation_id path usage through the endpoint template. It does not explain the optional profile parameter or when a non-default profile should be selected, leaving that entirely to the schema.

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, "Read a fleet," and immediately enumerates the fleet-level content returned: master device, mirror push count, inherited settings, and overdue alert. It also explicitly distinguishes this from listFleetDevices by noting that sibling has each member, so an agent can route between them without opening schemas.

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 makes the usage context clear: use this for fleet summary/status data and use listFleetDevices when individual members are needed. It does not spell out exclusions or prerequisites, but the sibling routing is explicit enough for correct selection.

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