jobq_add_scheduling

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only notes that this is a Pro feature and says 'Generate', but does not disclose whether it writes files, modifies configuration, requires an API key, or has side effects. The behavior is largely opaque.

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 front-loaded sentence with no filler words. It is concise and easy to parse, though the brevity also contributes to under-specification in other dimensions.

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, and only one described parameter, the description leaves major gaps: what the generated scheduling looks like, whether files are created or modified, what the directory must contain, and whether api_key is mandatory for the Pro feature. An agent calling this tool would be guessing at the expected behavior.

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%, and the description adds no parameter-level meaning. The required 'directory' is only described as 'Project directory' in the schema, and 'api_key' has no description at all. The description does not compensate for the missing api_key semantics or clarify how these parameters relate to scheduling/priorities.

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 ('Generate') and a clear resource ('job scheduling and priorities'), and the 'jobq' prefix plus sibling names make the domain obvious. However, it does not explicitly differentiate from siblings like jobq_setup_bullmq or jobq_setup_workers, and it does not say what artifact is produced.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no indication of whether it should follow jobq_setup_bullmq or jobq_setup_workers. The '(Pro feature)' hint is the only contextual signal, which is insufficient for routing.

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