Get Layer Features

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

Annotations include readOnlyHint=true, which matches the read-only nature. The description adds value by detailing the structure of returned data, filtering syntax, limit constraints, paging via offset, and optional geometry inclusion. It provides behavioral context beyond annotations.

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 well-structured paragraph that starts with the main purpose, then details the return structure, and lists parameters with constraints. It is efficient and not verbose, though slightly dense.

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 presence of an output schema, the description need not fully detail return values. It covers all five parameters and the return format sufficiently. The description is complete for a data retrieval tool, though it could mention that layer_id is required.

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 description coverage is 0%, so the description bears the full burden. It clearly explains layer_id (implicit), limit (max 50, default 10), offset (paging), expression (QGIS expression syntax with examples), and include_geometry (adds _geometry key). This adds significant meaning beyond the schema's type/default.

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 it retrieves features from a vector layer, specifies the return format (flat dicts with _fid and attributes), and distinguishes it from siblings like add_features, delete_features, update_features, and select_features.

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 explains the tool's capabilities (filtering, paging, geometry inclusion) but does not explicitly state when to use it over alternatives like select_features or get_selection. It provides implied guidance but lacks clear exclusions or comparison with siblings.

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