get_project_info

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Retrieve' implies a read-only action, but the description does not say what metadata is returned, how the project path is validated, or whether the tool scans/reads files versus just returns cached info.

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, efficient sentence with no filler and front-loads the core action. It could carry more useful detail, but as a concise statement it is appropriately short.

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 and no annotations, the description does not explain what 'metadata' includes, what the invocation returns, or how this tool relates to the many Godot siblings. For a correctly selectable and callable tool, this leaves a material gap.

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%, so projectPath is already documented as 'Path to the Godot project directory.' The description adds no additional meaning beyond the schema, so it lands at the baseline of 3.

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 identifies the action ('Retrieve') and the resource ('metadata about a Godot project'), so an agent can tell this is a read-oriented project-info tool. However, 'metadata' is vague and the description does not explicitly differentiate it from siblings like list_project_files, get_scene_insights, or get_godot_version, so it stops short of a 5.

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?

There is no guidance on when to use this tool versus related siblings, no stated prerequisites, and no exclusions. The sibling list contains several information-retrieval tools, but the description gives no routing help at all.

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