project_settings

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

The annotation readOnlyHint: false indicates potential write operations, and the description confirms 'set (modify settings)'. However, it does not disclose possible destructive consequences of modifying settings, whether changes are reversible, or if specific permissions are required. With no further annotations, the description should provide more behavioral context for a mutation tool.

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 concise: two short sentences. The first sentence states the purpose, the second lists actions and categories. No redundant information. Front-loaded with essential info.

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?

Despite having a clear purpose and schema, the description lacks details about the output format for 'get' and 'list_categories' actions. Given no output schema, the agent does not know what shape of data to expect. Additionally, there is no mention of how to use the 'settings' parameter (key-value pairs) in the description, although the schema covers it. The description should provide more complete guidance for a tool with multiple actions.

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% with descriptions for all parameters, so the baseline is 3. The description adds value by listing the actions and categories, which correspond to the 'action' and 'category' parameters, but it does not add meaning beyond what the schema already provides. The mapping is clear but not enhanced.

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 states it manages Unity Project Settings, lists the exact actions (get, set, list_categories), and enumerates the supported categories (player, quality, etc.). It distinguishes itself from sibling tools which are more specific to individual features (e.g., physics, animation) by covering a broad umbrella of settings.

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?

The description lists the actions and categories, so an agent knows what operations are possible. However, it does not explicitly state when to use this tool versus more specific tools (e.g., for physics settings, should one use project_settings or the physics tool?). It provides clear context but lacks explicit exclusion criteria or alternative recommendations.

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