get_project_context

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic purpose without revealing side effects, access requirements, or what exactly constitutes 'project context'. No information on mutability, permissions, or return structure is given.

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 short sentence, which is concise and front-loaded. However, it could be slightly expanded to include what the context covers without becoming verbose. Every word earns its place.

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 the lack of output schema and the tool's likely complex return value (e.g., project settings, structure), the description is insufficient. It does not explain what 'project context' includes, leaving the agent to guess. For a simple info tool, more completeness is needed.

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?

There are zero parameters, so the schema coverage is effectively 100% by default. The description does not add parameter-specific meaning, but no additional detail is necessary for an empty parameter set. Baseline score of 4 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?

The description states 'Get Godot project context' with a specific verb and resource, but 'context' is vague and does not specify what aspects of the project are included. It distinguishes from editing-focused sibling tools like add_node or delete_node by implying a read-only information retrieval function.

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?

No guidance on when to use this tool versus alternatives like get_scene_tree or get_input_map. There is no mention of prerequisites, suitable contexts, or when not to use it. The description provides no usage recommendations.

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