fleet_hosts

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the critical safety trait 'No host is contacted' and identifies fleet.yaml as the source, but it omits whether local files are modified, permission requirements, and return/pagination behavior. Adequate but with clear gaps.

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?

Three short sentences, front-loaded with the resource and contents, followed by the key safety constraint and usage pointer. Every sentence earns its place with no redundant 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?

There is no output schema, and the description does give a return-shape hint ('hosts with address, roles, tags, groups, services'). However, it does not mention the richer details fields such as logs, policy, and bootstrap settings, and does not describe pagination or permissions. Complete enough for a simple inventory tool, but not fully comprehensive.

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 100%, so both the target filtering syntax and the details flag are fully documented in the schema. The description mentions host attributes but adds no parameter meaning or syntax beyond what the schema already provides; the baseline 3 applies.

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 resource — the fleet.yaml inventory of hosts and their address, roles, tags, groups, services. It distinguishes itself from sibling host-* tools by explicitly saying 'No host is contacted' and positions itself as the starting point for names used by other tools.

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?

Explicitly says 'Start here to learn the names used by every other tool,' which gives clear first-step guidance. It also implies when to prefer it over host-contacting siblings via 'No host is contacted,' but it does not name a specific alternative or state exclusions.

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