List Processing Algorithms

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

The readOnlyHint annotation already indicates a safe read operation, so the description's main contribution is specifying the returned fields (id, name, provider). It does not describe pagination, sorting, or limit behavior, which would be helpful but not critical given the tool's simplicity.

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 two succinct sentences with no wasted words. It front-loads the action and then lists the return fields, making it easy to parse.

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 tool has only two optional parameters and an output schema, the description covers the core purpose and return. However, it lacks parameter formatting details and does not explain the output schema structure beyond mentioning three fields. It is adequate but not comprehensive.

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 must compensate. It hints that 'search' is a keyword and 'provider' is a provider name, but lacks details on matching behavior (e.g., exact match, partial match, case sensitivity) or valid values for provider. This is insufficient for precise parameter usage.

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 specifies the verb 'Search' and the resource 'processing algorithms', with optional filtering by keyword and/or provider. It also states the return fields (id, name, provider), which distinguishes it from sibling tools like get_processing_providers or get_algorithm_help.

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 implies usage context by mentioning filtering by keyword/provider, but does not explicitly state when to use this tool versus alternatives such as list_processing_models or get_algorithm_help. No exclusions or prerequisites are provided.

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