fly_list_apps

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 the basic action (list apps) without disclosing behavioral traits such as authentication requirements, rate limits, or the effect of omitting org_slug. For a listing operation, it is likely read-only, but this is not stated.

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?

Very concise single sentence that is front-loaded. However, it is so minimal that it sacrifices completeness. Every word earns its place, but additional context could be added without significant bloat.

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?

With no output schema and no annotations, the description is sufficient for a simple list operation but lacks behavioral details like authentication, scope of 'your organization', and whether the list is paginated. It meets a minimal viable standard but has 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 coverage is 100% with descriptions for both parameters. The description adds no meaning beyond the schema; it does not explain how org_slug affects results or that api_key is needed for auth. Baseline 3 is appropriate since schema handles parameter info.

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 uses a specific verb ('List') and resource ('apps'), clearly stating it lists all Fly.io apps in the organization. It distinguishes from sibling tools like fly_get_app (single app) and fly_list_machines (different resource).

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?

No guidance on when to use this tool vs alternatives. The description does not mention conditions for using the optional org_slug or explain that api_key is required for authentication. Siblings are present but not referenced.

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