stellaris_queue_add

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

No annotations are provided, so the description carries the full behavioral burden. It indicates a queue mutation but does not disclose duplicate handling, queue persistence, permissions, side effects, or what happens on invalid titles.

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 clear sentence with the action front-loaded. Every word earns its place and there is no unnecessary text.

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?

For a simple two-parameter queue mutation, the description covers the core action and tier. However, with no annotations and no output schema, it leaves behavioral gaps around duplicates, errors, and return behavior that would help an agent invoke it confidently.

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 50%: the tier parameter is documented in the schema, while titles has no schema description. The description names both parameters and says tier 1 is highest, but it does not add meaningful format or behavior details for the titles array.

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 states a specific verb and resource: add titles to the download queue, with an optional priority tier. It clearly conveys the action, though it does not explicitly distinguish this from sibling tools such as stellaris_queue_next.

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 explains what the tool does but gives no guidance on when to use it versus alternatives like stellaris_live_fetch or stellaris_queue_next. There are no exclusions, prerequisites, or usage context.

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