set_gp_stroke_settings

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Best-effort' hints at possible failure but does not specify what happens on failure, whether the operation is destructive, or what effects it has on the scene. No side effects or error behavior are disclosed, which is unacceptable for a mutation-like 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 extremely short (one sentence), which is efficient but borders on under-specification. It does not front-load any critical information beyond a vague purpose. Unlike a truly concise description that packs meaning into few words, this lacks substance, so it scores below adequate.

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 tool's complexity (3 parameters, 0% schema coverage, no annotations, and a specific target of GP stroke settings), the description is severely incomplete. It does not mention prerequisites (e.g., object must be a GP object), expected input formats, or what the output means. Even with an output schema, an agent cannot infer correct usage from this description.

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% for the three parameters (color, strength, object_name). The description mentions 'material/color' which loosely maps to the color parameter, but it does not explain strength or object_name at all. It adds no meaningful semantic value beyond what a user might infer from the names, failing to compensate for the poor schema coverage.

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 a verb ('setup') and a resource ('material/color for GP'), making the core purpose somewhat clear. However, it is vague: 'best-effort' and 'material/color' do not explicitly mention stroke settings, and it does not differentiate from sibling tools like set_principled_bsdf or assign_material. The name gives more specificity than the description, which only loosely paraphrases it.

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. There is no mention of prerequisites (e.g., an existing Grease Pencil object), no exclusions, and no alternatives named. 'Best-effort' implies a caveat but does not explain the conditions under which it should be selected.

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