set_project_settings

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

With no annotations, the description carries the full behavioral burden. It implies mutation but says nothing about persistence (immediate vs. saved on project save), whether changes affect existing caches, or reversibility. For a project-level settings mutation, that is a substantial gap.

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?

Very short and front-loaded, but the trailing 'etc.' is wasted and actively introduces ambiguity about what else can be set. Brevity here comes at the cost of specification rather than from efficiency.

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?

A mutation tool with no annotations, no output schema, and only two optional params needs the description to explain effect scope and persistence. It does not, so an agent cannot predict what changing GPU renderer does to an open project.

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 both parameters are already documented, giving the baseline 3. The description's mention of 'scratch disks' loosely maps to scratchDiskPath but adds nothing about the gpuRenderer enum's three choices, which is already fully covered by the schema.

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 the verb 'Modify' and resource 'project settings', which is understandable, but 'settings' is a broad category and the parenthetical '(scratch disks, etc.)' leaves the scope fuzzy. It does not distinguish this from adjacent project-level tools like set_workspace, set_label_defaults, or flush_cache.

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 indication of when to reach for this tool versus alternatives, no prerequisites, and no note about whether settings apply immediately or require a save/restart. The agent must infer usage entirely.

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