fly_list_machines

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

No annotations are provided, so the description carries the full burden. It only states 'List all machines', implying a read operation, but fails to disclose any behavioral traits such as pagination, rate limits, or whether it returns deleted machines by default. The description is too minimal to be sufficient.

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 of 6 words with no redundant information. However, it sacrifices necessary detail for brevity, making it less informative than it could be.

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?

Given 3 parameters, no output schema, and no annotations, the description is insufficient. It does not explain how to use the parameters together, what the output format is, or any constraints. An agent would lack critical context to use the tool correctly.

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?

With 0% schema description coverage, the description should add meaning to parameters, but it only mentions 'machines in a Fly.io app'. It does not explain the role of 'api_key', 'app_name', or 'include_deleted' (e.g., what 'include_deleted' does). The description fails to compensate for the lack of parameter documentation.

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 'List all machines in a Fly.io app' clearly states the tool's purpose with a specific verb-list and resource-machines within a Fly.io app context. It distinguishes itself from sibling tools like fly_create_machine, fly_get_app, fly_list_apps, and fly_list_volumes.

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 provides no guidance on when to use this tool versus alternatives, such as fly_list_apps or fly_list_volumes. It lacks any mention of prerequisites, required permissions, or scenarios where this tool is appropriate.

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