skylight_list_auto_creation_intents

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

No annotations are provided, so the description carries full burden. It does not disclose whether this operation is read-only, what ordering or filtering (if any) applies, pagination behavior, or the effect of calling it. The phrase 'on the frame' is vague and doesn't clarify scoping for the optional frameId parameter.

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 sentence of 14 words, which is concise but lacks structure. It front-loads the verb and resource, but the brevity sacrifices clarity on key details like parameters and sibling differentiation.

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 no annotations, no output schema, one optional parameter, and related sibling tools (list drafts, list items, get intent), the description is incomplete. It does not explain the differences between intents, drafts, and items, nor does it describe the output format or whether the list is scoped to a specific frame. The agent lacks sufficient context to use the tool correctly.

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%, and there is one optional parameter frameId. The description mentions 'on the frame' but does not explain the parameter's role or behavior when omitted. It fails to specify whether frameId filters results or returns all intents across frames, which is necessary for the agent to use the parameter correctly.

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 verb 'list' and the resource 'AI auto-creation intents', and adds context about finding pending/completed drafting jobs and their IDs. However, it does not differentiate this tool from sibling tools like skylight_list_auto_creation_drafts or skylight_list_auto_creation_items, leaving room for confusion.

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 provides no guidance on when to use this tool versus alternatives such as skylight_get_auto_creation_intent or skylight_list_auto_creation_drafts. It only implies usage for discovering intents but lacks explicit context or exclusions.

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