matlab-mcp-server-python

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. It mentions the return format ('list of job summaries including status and timing'), which is helpful, but lacks critical details: whether this is a read-only operation, if it requires authentication, any rate limits, pagination behavior, or error conditions. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 states the purpose, the second describes the return value. No wasted words, front-loaded with the core functionality, and appropriately sized for a simple listing tool.

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 simplicity (0 parameters, output schema exists), the description is reasonably complete. The output schema will document return values, so the description doesn't need to detail them further. However, with no annotations and behavioral gaps (e.g., safety, limits), it could provide more context about operational constraints for a production environment.

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 tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the lack of inputs. The description appropriately doesn't add parameter information beyond what the schema provides, maintaining focus on the tool's purpose and output. This meets the baseline expectation for zero-parameter tools.

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 ('List all jobs') and resource ('for the current session'), with a specific verb+resource combination. It distinguishes from siblings like 'get_job_status' or 'get_job_result' by focusing on listing all jobs rather than querying specific job details. However, it doesn't explicitly differentiate from all siblings (e.g., 'list_files' has similar structure but different domain).

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 ('for the current session') but doesn't provide explicit guidance on when to use this tool versus alternatives like 'get_job_status' or 'get_job_result'. No when-not-to-use scenarios or prerequisites are mentioned, leaving usage decisions to inference from the tool name and context.

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