Get Project Info

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the environment prerequisite (IDE running, project open) and the return shape (one fact per line). That is meaningful context an agent needs before calling, though it says nothing about failure behavior when no project is open.

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 sentences, front-loaded with what is returned and followed by the call-ordering rule. The field enumeration is dense but each item maps to a real return value; only the version/Agentic Mode detail borders on surplus.

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 must describe the return payload — and it does, item by item. Combined with the stated prerequisite and the sequencing advice relative to lint_project_file, an agent has everything needed to call this correctly.

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 there is nothing for the description to disambiguate; baseline is 4. The description correctly implies a no-argument call by describing output only.

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 ("Returns facts about the project open in the Xojo IDE") and enumerates exactly which facts: project path, project directory, Xojo version, selected location and type, Agentic Mode state. That enumeration separates it from siblings like get_current_location and get_code, which return only a subset.

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?

"Call it first when working on files on disk" gives explicit ordering guidance and names the dependent tools (lint_project_file, direct edits) that need absolute paths. It also states the prerequisite that the IDE must be running with the project open. No explicit when-not-to-use case, so it falls short of a 5.

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