project_settings

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing: not whether it mutates, whether it requires an open project, whether changes persist, or what it returns. The fragment mentions 'transparent' being allowed for background, which is the only behavioral hint, and it is minimal.

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?

Brevity here reflects under-specification rather than information density; the text is a fragment with no front-loaded purpose statement. It is short but does not earn its place as a usable definition.

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 annotations, no output schema, and 0% parameter coverage, the description is the only information source and it is a four-word fragment. For a tool with four parameters that likely mutates project state, this is wholly inadequate.

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 must compensate, but it only names three of the four parameters (name, background, dpi) and omits 'project' entirely. It adds one useful constraint ('transparent' allowed for background) but leaves types, formats, and defaults undocumented.

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 is a bare noun phrase listing settings fields ('Document name, background color, dpi') with no verb, so it never states what the tool actually does. It neither says whether project_settings reads or writes configuration, making it effectively a restatement of the tool name rather than a purpose statement.

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 about when to use this tool versus siblings like comfy_settings or project_info, and no prerequisites or exclusions are mentioned. An agent has no basis to choose this tool over alternatives from the description alone.

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