List Project Items

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

Goes well beyond the annotations (which already cover readOnly/idempotent/non-destructive): it discloses the return shape (tab-separated names), the empty-result and nonexistent-location behavior (a message, not an error), the Xojo 2026r3 limitation on member listing, and the environmental prerequisite. That is the class of information an agent cannot get from structured fields.

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 core scope is front-loaded in the first clause, and each subsequent sentence carries a distinct fact (member limitation, empty-result behavior, prerequisite). It is dense but four sentences of similar weight, so the priority ordering is slightly flatter than ideal.

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, the description responsibly covers return format (tab-separated names), soft-failure messages, and the required IDE state. Minor residual ambiguity remains about whether the response is a single tab-delimited string or a list of records, and about ordering of the returned items.

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% and the property description already documents the dot-separated path and omitting for top level. The description explains what happens semantically when location is empty versus a folder, but largely restates the schema rather than adding format, edge-case, or naming-example detail beyond it. Baseline 3 applies.

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 and resource ("Lists the project items directly under a location in the open Xojo project's Navigator") and immediately defines the two scoping modes (top level when location is empty, folder contents otherwise). It also carves out what it does NOT return (item members), and names the sibling tool get_project_info that supplies the folder paths, so it is distinguishable from neighbors without opening a schema.

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?

Clear context for use: call it to enumerate Navigator contents, and for member information the description redirects to reading .xojo_code/.xojo_window via get_project_info. It also states the prerequisite (Xojo IDE running with the project open). It stops short of explicitly excluding any sibling that might look like an alternative enumerator, so it is not a full when/when-not map.

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