list_gp_layers

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It hides whether the operation is read-only, what side effects it might have, and what the return value is. The description adds zero behavioral information beyond the tool name.

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?

While the text is short, it is under-specified rather than concise. The single sentence 'Blender Studio Pro MCP: list_gp_layers' carries no meaningful content and wastes the opportunity to provide any useful details.

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?

This tool has one parameter, a non-trivial function (listing grease pencil layers), and no annotations. The description provides nothing to help an agent understand what the tool does, when to call it, or what it returns. It is completely 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?

The sole parameter 'object_name' is undocumented in the schema and not mentioned in the description. With schema description coverage at 0%, the description provides no clue about the expected format, meaning, or purpose of this parameter.

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 essentially a repetition of the tool name with a prefix. It does not state what is being listed, what 'GP' stands for (grease pencil), or what the tool accomplishes. There is no verb or resource specificity—it is a tautology.

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 on when to use this tool versus alternatives. While sibling tools like add_gp_layer and set_gp_stroke_settings exist, the description does not mention any context, prerequisites, or exclusions.

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