qgis_list_algorithms

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

Since no annotations are provided, the description discloses key behaviors: case-insensitive matching, default limit of 50 with hard max of 200, and the returned id usage. It does not mention any side effects but as a list tool, none are expected.

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 with no filler. It front-loads the purpose, then adds filtering and limit behavior, and ends with cross-tool guidance. Every sentence earns its place.

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?

For a listing tool with two parameters and an output schema, the description is adequately complete: it explains filter behavior, limit constraints, and how to use results. It does not detail the output structure, but the output schema likely covers that.

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 adds essential meaning: text_filter matches against id, name, group; limit defaults to 50 with a 200 hard max. This compensates well for the schema gap.

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 tool lists Processing algorithms available in the QGIS install, with specific verb and resource. It distinguishes from siblings by focusing on algorithms, not layers or 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 explicitly guides the agent to use the returned id with qgis_algorithm_help and qgis_run_algorithm, and advises narrowing the filter rather than raising the limit. However, it lacks explicit when-not-to-use guidance.

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