tdarr_search_flow_templates

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

With no annotations present, the description must disclose behavioral traits. It only states 'Search flow templates' without mentioning whether it is read-only, what the search criteria do, what is returned, or any side effects.

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 extremely concise at three words, with no unnecessary content. It is front-loaded and easy to parse, though it sacrifices completeness for brevity.

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's two required parameters and no output schema, the description should provide more context about the search functionality, such as how the search string and plugin type filter interact, and what the response looks like. The current description is insufficient for an agent to use the tool correctly without additional schema clues.

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%, so both parameters are described in the input schema. The description adds no additional meaning beyond the parameter names and types, earning the baseline score of 3.

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 'Search flow templates' clearly states the verb 'Search' and the resource 'flow templates', distinguishing it from sibling 'tdarr_search_flow_plugins' which searches plugins. However, it is very brief and lacks any additional detail about the scope or nature of the search.

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?

No guidance is provided on when to use this tool versus alternatives like 'tdarr_search_flow_plugins' or other search tools. There is no context on prerequisites, limitations, or best practices.

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