matlab-mcp-server-python

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 adds useful context about what information is returned (status, timing info, optional progress from .progress file), which helps the agent understand the tool's behavior beyond basic schema. However, it doesn't mention error conditions, rate limits, authentication needs, or whether this is a read-only operation (though 'get' implies it likely is).

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 perfectly concise with two sentences that each earn their place. The first sentence states the core purpose, and the second sentence provides valuable additional context about what information is returned. No wasted words or redundant information.

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 the tool's moderate complexity (status checking with progress monitoring), no annotations, and the presence of an output schema (which handles return value documentation), the description provides adequate context. It covers the purpose, return information, and usage context. The main gap is lack of explicit behavioral constraints or error handling information.

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?

The input schema has 1 parameter with 0% description coverage, so the description must compensate. While it doesn't explicitly explain the 'job_id' parameter, the context ('Get the status of a MATLAB execution job') strongly implies that 'job_id' identifies the specific job to query. This is adequate semantic context for a single parameter tool, though not explicitly documented.

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 tool's purpose as 'Get the status of a MATLAB execution job' with specific verb ('Get') and resource ('MATLAB execution job'). It distinguishes from siblings like 'get_job_result' (which presumably returns job outputs) by focusing on status information. However, it doesn't explicitly differentiate from 'list_jobs' which might also provide status information for multiple jobs.

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 implies usage context by mentioning 'for running jobs,' suggesting this tool is primarily for monitoring active executions. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'get_job_result' (for completed jobs) or 'list_jobs' (for multiple jobs). No exclusions or prerequisites are mentioned.

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