get_gp_info

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

Annotations include readOnlyHint=true, and the description ('Get info') aligns without contradiction. The description adds a useful preview of returned content (layers, frames, stroke count) but does not disclose error behavior, object type requirements, or result formatting details, which would be valuable beyond the annotation.

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, front-loaded sentence that efficiently conveys the core purpose and key data points with no redundant words. Every word earns its place.

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?

Despite being a simple tool with an output schema, the description fails to clarify the sole required parameter, leaving a significant usability gap. The absence of parameter guidance makes the tool incomplete for an agent to invoke correctly, even though the output schema exists.

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 0% description coverage, and the description does not explain the 'object' parameter at all. The agent is left to guess whether 'object' refers to a name, ID, path, or some other identifier, making correct invocation highly uncertain.

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 clearly states the tool's purpose: 'Get grease pencil info: layers, frames, stroke count.' It specifies a concrete verb ('Get'), a resource ('grease pencil info'), and precise data items, effectively distinguishing it from sibling tools like get_object_info.

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?

The description implies usage for retrieving grease pencil-specific data but does not explicitly state when to use this tool versus alternatives such as get_object_info or add_gp_layer. No exclusions or when-not scenarios are mentioned, so guidance is only implied.

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