Get Layer Features

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

The description goes beyond the readOnlyHint annotation by detailing output structure, filter pattern, pagination behavior, and geometry handling. This fully discloses the tool's read-only nature and operational characteristics.

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 efficiently convey the tool's purpose, output format, and key parameters with examples. No extraneous information, well-front-loaded.

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 output schema exists (so return values are documented elsewhere), the description sufficiently covers all input parameters, constraints, and behavioral traits. It is complete for a read-only data retrieval 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?

Despite 0% schema description coverage, the description explains all five parameters: layer_id (implied as required), expression (QGIS syntax), limit (max 50, default 10), offset, and include_geometry. This adds significant value beyond the raw schema.

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 output format (flat dicts with _fid and attributes), and distinguishes from sibling tools like delete_features or select_features by its read-only nature and parameter focus.

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 clear usage context, including expression filter syntax, limit defaults and maximum, offset for paging, and geometry inclusion option. It lacks explicit alternatives or when-not-to-use, but the constraints (e.g., max 50 limit) guide proper invocation.

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