JPI MCP Server

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Create' implies a write/mutation operation, the description doesn't address critical behavioral aspects like required permissions, whether the operation is atomic/transactional, error handling for partial failures, rate limits, or what happens to existing tasks. The batch nature is mentioned but without operational details.

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, efficient sentence that communicates the core functionality without unnecessary words. It's appropriately sized for a tool with one parameter and good schema documentation, though it could benefit from additional context about usage and behavior.

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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't address behavioral expectations, error conditions, response format, or differentiation from similar tools. The 100% schema coverage helps with parameters, but critical operational context is missing for a batch creation operation across multiple jobs.

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%, with the schema clearly documenting that 'tasks' is a required array of task objects with jobGuid. The description adds minimal value beyond this, only implying the cross-job nature through 'across multiple jobs' but not providing additional context about task object structure or jobGuid requirements beyond what the schema already states.

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 ('Create tasks') and scope ('across multiple jobs in a single batch operation'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'jpi_add_tasks_batch' or 'jpi_add_task', which appear to handle similar task creation operations, leaving some ambiguity about when to choose this specific tool.

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. With multiple sibling tools for task creation (e.g., jpi_add_task, jpi_add_tasks_batch, jpi_add_component_task), there's no indication of when batch creation across multiple jobs is preferred over other methods, nor any mention of prerequisites or exclusions.

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