Create Memory Layer

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

With no annotations, the description only reveals that the layer is 'in-memory', but does not disclose transient nature, potential loss on project close, authorization needs, or side effects. Limited behavioral detail beyond allowed values.

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 with key information front-loaded. Could be more structured (e.g., bullet points) but remains efficient without unnecessary verbiage.

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 no output schema, description lacks information on return value (e.g., layer ID). Does not address error handling. Adequate for a simple creation tool but not fully comprehensive.

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?

Schema has 0% description coverage, so description adds value by enumerating allowed geometry types and field structure. However, it does not explain 'name' or 'crs' parameters, leaving half of parameters undocumented.

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 'Create a new in-memory vector layer', providing a specific verb and resource. It lists supported geometry types and field definitions, distinguishing it from sibling tools like add_raster_layer or add_vector_layer.

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 on when to use this tool versus alternatives like add_vector_layer or create_layer_group. Missing context on prerequisites or scenarios where in-memory layers are appropriate.

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