Get Active Layer

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

The description confirms a read operation, consistent with annotations (readOnlyHint: true). It adds context about 'active (selected)' layer, but does not disclose behavior when no layer is active or potential errors.

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?

Single sentence that is direct and free of unnecessary words. Clearly communicates the tool's purpose without redundancy.

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 zero parameters and presence of an output schema (not shown but indicated), the description is sufficiently complete. However, it could briefly mention the return format (e.g., layer reference or name).

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?

No parameters in the schema; the description correctly omits param details. With 100% schema coverage and no params, the description adds no extra meaning, but baseline is appropriate.

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 verb 'Get' and the resource 'currently active (selected) layer in the QGIS layer panel', specifying exactly what the tool retrieves. It distinguishes itself from siblings like 'get_layers' and 'set_active_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 such as 'get_layers' or 'find_layer'. Does not mention if it should be called before certain operations or what happens when no layer is active.

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