layer

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

Annotations provide readOnlyHint=false, indicating potential mutations, which aligns with operations like 'create' and 'set_properties'. The description adds value by listing specific operations and their required data parameters, giving context about what actions are possible. However, it doesn't disclose additional behavioral traits like permission requirements, side effects, or error handling beyond what annotations imply.

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 front-loaded with a clear purpose statement followed by a bulleted list of operations and their data requirements. It's efficiently structured with zero wasted sentences, though the bulleted format could be slightly more polished for readability.

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 tool's complexity (multiple operations with varying data needs), 0% schema coverage, and the presence of an output schema, the description does a decent job. It covers operation types and data structures but lacks details on error cases, permissions, or how operations interact. The output schema likely handles return values, but more behavioral context would improve completeness.

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?

With 0% schema description coverage, the description carries the full burden of explaining parameters. It effectively details the 'operation' parameter with specific values (list, create, etc.) and outlines the 'data' structure for each operation (e.g., {name, color?} for create). This compensates well for the schema gap, though it doesn't explicitly cover the 'include_screenshot' 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 clearly states the tool's purpose as 'Layer creation and management' and lists specific operations (list, create, set_current, etc.), which provides a clear verb+resource combination. However, it doesn't explicitly differentiate this tool from sibling tools like 'entity' or 'drawing' that might also manage CAD elements, so it doesn't reach the highest level of sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives. It lists operations but doesn't explain when to choose 'layer' over sibling tools like 'entity' or 'annotation', nor does it mention prerequisites or exclusions for specific operations. This leaves the agent with minimal contextual guidance.

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