Search Compeller generation jobs by title for the authenticated account.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results to return (default 20) | |
| query | Yes | Search query to match against compel titles |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations include readOnlyHint=true, which already indicates a safe read operation. The description adds minimal context ('for the authenticated account') but does not disclose behavior such as return format, pagination, rate limits, or whether the search is case-insensitive or partial matching.
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 a single focused sentence with no unnecessary words. It is concise and front-loaded with the action, though the ambiguous 'Compeller generation jobs' could be tightened.
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 tool is simple with only two parameters and a readOnlyHint, but the description lacks context about return values, how it differs from 'list_compels', and the exact matching behavior. It is sufficient for basic invocation but leaves gaps for an agent to select it correctly among siblings.
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 100%: both 'query' and 'limit' have clear descriptions. The description adds no significant semantic detail beyond the schema; it only restates that search is by title, which is already in the query parameter description.
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 action (Search) and the resource (Compeller generation jobs), with an explicit scope (by title, for the authenticated account). However, the term 'Compeller generation jobs' is slightly ambiguous and it does not explicitly differentiate from the sibling tool 'list_compels', which likely returns all compels.
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 given on when to use this tool versus the alternative 'list_compels' or other search tools. The description does not mention any prerequisites, exclusions, or situations where this tool is preferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Every tool targets a distinct action or resource. Groups like compels, lighting cues, webhooks, and account are clearly separated, and even similar tools (create_compel vs create_compel_from_music) have well-defined differences in input source.
All tool names follow a consistent verb_noun pattern with underscores (e.g., cancel_compel, launch_lighting_cue, register_webhook). No mixing of conventions or ambiguous verb choices.
With 30 tools, the server is above the 25+ threshold for 'too many'. While the scope includes multiple subdomains, the high number adds cognitive load and risks selection errors for an agent.
Core workflows are present (create, read, cancel, list, search, render), but missing update/delete for compels and media, and no way to modify render configuration beyond defaults.