create_grease_pencil

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the creation action and does not mention scene insertion, data-block creation, active-object changes, or name-collision behavior.

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 a single direct sentence with no filler and is easy to parse. However, it is so terse that it leaves behavioral and usage gaps, so it is concise but not fully informative.

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?

An output schema exists, so return values need not be described. For a two-parameter creation tool this is near-minimal viable, but missing context about how and where the object is created and how it relates to existing grease pencil objects leaves clear gaps.

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%, and the description does not mention name or location at all. While the parameter names and defaults are fairly self-explanatory, the description should have compensated for the missing schema descriptions and does not.

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 a clear verb ('Create') and resource ('grease pencil object'), which distinguishes it from generic create_object and from create_gp_stroke/add_gp_layer that operate on strokes or layers. It is specific enough, though it stays at the phrase level without elaborating on what 'grease pencil object' includes.

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 is given on when to use this tool versus alternatives such as create_object, create_gp_stroke, or add_gp_layer. The description provides no context, prerequisites, or selection criteria.

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