skydemon_list_flightplans

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

No annotations are provided, so the description must carry behavioral load. It does disclose that the operation is read-only and that it defaults to a local disk path, which is useful context. However, it omits what happens if the directory is missing, the output format, or whether it recurses.

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?

Two short clauses front-load the core action and scope, with zero filler. Every phrase earns its place.

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 zero-parameter, no-output-schema tool, the description covers the essential scope (local disk, read-only, default path). It is nearly complete; naming the cloud sibling would fully disambiguate the choice.

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?

The tool takes zero parameters, so the baseline is 4. The description appropriately mentions the default path (~/Documents/SkyDemon/Routes), which is the only path-related behavior an agent needs to know. There are no parameters requiring further explanation.

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 (List) and resource (saved flightplans), and clarifies disk scope versus the sibling skydemon_list_cloud_flightplans. It implies but does not name the cloud alternative explicitly, so an agent must infer the contrast.

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?

Usage is implied: 'read-only' and 'on disk' suggest a safe local listing operation. But there is no explicit when/when-not guidance or pointer to skydemon_list_cloud_flightplans, so the agent must infer which listing tool to pick.

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