geometry-create_grease_pencil

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

With no annotations available, the description carries the full burden of behavioral disclosure, but it only states 'Create a grease pencil object.' It does not explain what happens to existing objects, how the object is positioned, what the return value is, or any side effects. This is a minimal, non-informative description for a creation 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 (5 words), which is under-specification rather than conciseness. It lacks critical details, so the brevity is not effective. Every sentence should earn its place, but here the single sentence provides almost no value.

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 complexity of the tool (7 parameters, multiple types, no output schema, no annotations), the description is severely incomplete. It fails to explain the object types, the purpose of each parameter, or any behavioral nuances, leaving the agent to guess or rely solely on the schema.

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?

The input schema has 7 parameters (name, type, scale, radius, location, rotation, use_in_front) but the description covers none of them (schema coverage 0%). The description adds no meaning beyond the schema's own titles and defaults, and does not compensate for the lack of parameter explanations.

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 clear verb ('Create') and specific resource ('a grease pencil object'), distinguishing it from sibling geometry creation tools like geometry-create_curve or geometry-create_text. However, it does not mention the variety of subtypes (e.g., STROKE, MONKEY, LINEART) that the 'type' parameter allows, which would make the tool's full scope clearer.

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 provided about when to use this tool versus alternatives. There are no explicit when-to-use, when-not-to-use, or alternative tool references. The description simply states what the tool does without context.

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