get_project_setting

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

Annotations already establish that this is read-only, non-destructive, and closed-world, so safety behavior is covered. The description adds useful behavioral detail beyond annotations: absent entries return stored:false, and the tool does not resolve defaults, feature tags, or override.cfg.

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 compact and front-loaded, stating the core read operation first and then the important behavioral caveats. Every clause carries useful information without unnecessary repetition.

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 rich annotations and an output schema already present, the description is reasonably complete on safety and return/absence behavior. However, because the input schema has no parameter descriptions at all, the lack of parameter-format guidance leaves a meaningful gap for an agent trying to invoke the tool 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?

Schema description coverage is 0%, so the description needs to clarify both parameters. It implies that setting is a project.godot expression and projectPath is the project location, but it does not explain the expected format for either, such as how setting keys should be written or whether projectPath must be absolute.

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 uses a specific read verb and names the resource precisely: a stored project.godot expression/setting. It also distinguishes the tool's scope from write-oriented siblings like set_project_setting and remove_project_setting by making clear this is a read operation.

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?

It gives clear usage context by saying the setting can be read without starting Godot, and it states important exclusions: defaults, feature tags, and override.cfg are not resolved. It does not name an alternative tool for those resolved-value cases, so it falls short of full when-to-use/when-not guidance.

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