openpipeline_matcher_autocomplete

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

With no annotations, the description explicitly declares the tool as 'safe, read-only,' which is a key behavioral trait. It does not disclose other details like auth needs or rate limits, but for an autocomplete tool, this is sufficient.

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 sentences with zero waste. It front-loads the action ('Get autocomplete suggestions') and immediately provides context for usage and safety.

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?

The description explains the tool's purpose and input but does not describe the output format (e.g., list of suggestions with metadata). However, given there is no output schema, the description is mostly complete for an autocomplete API.

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 coverage is 100%, and the description merely restates the parameter names and types ('query' and 'cursorPosition') from the schema. It adds no additional semantics beyond what the input schema already provides.

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 provides autocomplete suggestions for 'matcher (routing condition) expressions,' with the added context of being 'safe, read-only' and 'useful when authoring pipeline routing conditions.' This distinguishes it from sibling autocomplete tools like 'openpipeline_dql_autocomplete'.

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 indicates use when 'authoring pipeline routing conditions,' providing clear context. It does not explicitly state when not to use or name alternatives, but the sibling list includes a DQL-specific autocomplete, implying differentiation.

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