view_layers

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

Without annotations, the description fully describes the output format (ASCII map, piece IDs, empty dots) and optional range behavior. However, it omits details like output being plain text or how layers are separated, which could be inferred from an output schema.

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?

Two sentences, no wasted words. The first sentence establishes the core functionality, the second explains the optional parameters. Efficient and well-structured.

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?

The description, combined with the output schema presence, covers the main behavior and parameter usage adequately. It could expand on how multiple layers are displayed, but overall it is sufficiently complete for a simple read tool.

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 description adds meaning to the two parameters by explaining they define an optional plate range using bracket notation [z_from, z_to). With 0% schema coverage, this clarification is valuable, though it could specify inclusivity explicitly.

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 outputs a top-down ASCII map of plate layers with pieces shown by IDs and '.' for empty, and distinguishes it from siblings like export_build or list_parts. The verb 'view' and resource 'layers' are specific.

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 explicit when-to-use or when-not-to-use instructions are given. The optional range is noted but alternatives or prerequisites are not mentioned, leaving the context ambiguous for an agent.

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