Get Layer Features

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

The description adds value beyond the readOnlyHint annotation by detailing output format (flat dicts, _fid, attributes, optional geometry), parameter constraints (limit max 50, default 10), and paging behavior. This helps the agent understand what to expect from the tool.

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 concise (two sentences) and packs significant information. It is front-loaded with purpose and then details. A slight improvement could be using bullets for readability, but it remains effective without extraneous content.

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 (not shown but implied) and the readOnlyHint, the description covers output format, parameter details, and constraints. It lacks information on error handling for invalid expressions or edge cases, but overall provides sufficient context for a read-only feature 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?

With 0% schema description coverage, the description compensates well by explaining most parameters: limit (max 50, default 10), offset (paging), expression (with QGIS examples), and include_geometry (optional, _geometry key). However, it does not explain the required layer_id 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 'Get features from a vector layer', establishing a specific verb-resource pair. It distinguishes itself from sibling tools like add_features, delete_features, and select_features by focusing on reading features. The mention of return format (flat dicts with _fid and attributes) further clarifies the purpose.

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 some context about when to use the tool (e.g., with expression filter and paging), but does not explicitly state when not to use it or compare it to alternatives like get_selection or identify_features. The guidance is implied rather than explicit.

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