List recently saved PoB2 builds

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

Annotations already provide readOnlyHint=true, but the description adds valuable context: it is metadata only, the most recent file is a guess based on save recency, and it mentions configuration via POE2_POB_BUILDS_PATH. This goes beyond the annotation and accurately sets expectations.

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 two sentences, each earning its place: the first states the core function and sorting, the second clarifies the metadata limitation and the integration point with import_pob_build. No fluff or redundancy.

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 parameterless, read-only listing tool with no output schema, the description fully covers the agent's needs: what files are returned, the order, the reliability caveat, and how to consume the result. It also handles configuration details. Nothing essential is missing.

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 has zero parameters, so there is nothing to explain. Per the guidelines, a 0-parameter tool gets a baseline of 4. The description does not attempt to add parameter information because none exists.

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 verb 'List' and the resource '.xml files in the configured Path of Building 2 Builds folder', and distinguishes this from the sibling import_pob_build by noting it is metadata-only. It also clarifies the sorting order, making the tool's function unambiguous.

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 explicitly explains when to use this tool (to get a list of builds) and warns against interpreting the most recent file as the confirmed current build. It also directs the agent to pass a path to import_pob_build's filePath, effectively chaining tools and covering the follow-up action.

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