JPI MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Add' implies a write/mutation operation, it doesn't specify permissions required, whether the operation is atomic/all-or-nothing, what happens on partial failures, or what the response format looks like. For a batch mutation tool with zero annotation coverage, this is a significant gap.

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 front-loads the essential information: action, resource, and batch nature. There's zero wasted language or redundancy, making it optimally concise while still communicating the core purpose.

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 batch mutation tool with no annotations and no output schema, the description is insufficient. It doesn't address critical context like error handling, atomicity, response format, or performance characteristics. The agent lacks necessary information to use this tool effectively in production scenarios.

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%, so the schema already documents both parameters (jobGuid and jcrs array). The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain JCR object structure, validation rules, or batch size limits. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Add multiple Job Component References') and resource ('to a job') with the specific characteristic of being a batch operation. It distinguishes from the singular 'jpi_add_jcr' tool by emphasizing 'multiple' and 'batch', but doesn't explicitly differentiate from other batch operations like 'jpi_add_tasks_batch' or 'jpi_update_jcrs_batch'.

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 like the singular 'jpi_add_jcr' or other batch operations. There's no mention of prerequisites, performance considerations, or error handling for batch operations, leaving the agent without usage context beyond the basic purpose.

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