pio_list_targets

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. The description only says it lists targets, but it doesn't disclose the output format (even though an output schema exists, the description should mention that it returns a list of target names), whether it requires a specific project directory, or if it has side effects. It's a read operation but the description doesn't confirm there's no side effects. This is a minimal behavioral disclosure.

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 sentence that is concise and front-loaded with the main purpose (list extra build targets) followed by examples. There's no wasted words. It's appropriately sized for a simple listing tool.

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 that there are 2 parameters with zero schema descriptions, the tool's description is incomplete. An agent would likely not know how to fill in env or project_dir from the description alone. The output schema exists but the parameters are the gap. The tool is relatively simple, but the params are critical and undocumented.

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 0%, meaning the schema provides no descriptions for env or project_dir. The tool description also doesn't explain these parameters at all. The agent has no idea what values to pass (e.g., is env a target name or environment name? is project_dir a path?). The description completely fails to compensate for the zero schema coverage, leaving the parameters ambiguous.

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 clearly states the tool lists extra build targets for a project and provides concrete examples of those targets (buildfs, uploadfs, erase, etc.). The verb 'list' plus resource 'extra build targets' is specific. It distinguishes from siblings like pio_run_target (which executes targets) and pio_list_boards (which lists boards), though it could explicitly name a sibling for full differentiation.

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 implies usage for discovering available targets, which is a clear context, but it does not state when not to use this tool versus pio_run_target or other listing tools. No explicit alternatives or exclusions are mentioned, leaving the agent to infer that this is the right tool for listing targets versus running them.

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