Rowan MCP Server

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

With no annotations provided, the description carries full burden. It discloses that this is a workflow submission tool (implying it's a write operation that initiates calculations), mentions credit spending limits via max_credits, and describes what the tool returns (a workflow object). However, it doesn't cover important behavioral aspects like error conditions, timeouts, authentication requirements, or what happens with invalid inputs.

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 well-structured with clear sections (purpose, args, returns, example) and front-loaded with the main purpose. However, the Fukui indices explanation could be more concise, and some parameter details in the Args section slightly duplicate schema information. Overall efficient but with minor redundancy.

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 7-parameter workflow submission tool with no annotations and no output schema, the description provides adequate but incomplete context. It covers the purpose, parameters, returns, and includes an example, but lacks information about error handling, rate limits, authentication requirements, and detailed output structure. The absence of output schema means the description should ideally explain the workflow object structure more thoroughly.

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 all 7 parameters thoroughly. The description adds minimal value beyond the schema - it provides example values for optimization_method and fukui_method options, and clarifies that solvent_settings is a JSON string. However, it doesn't add significant semantic context beyond what's already in the parameter descriptions.

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 specific action ('Submit a Fukui indices calculation workflow') and resource ('using Rowan v2 API'), distinguishing it from siblings like submit_admet_workflow or submit_basic_calculation_workflow. It explicitly mentions calculating Fukui indices to predict molecular reactivity, which is a distinct computational chemistry task.

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 clear context for when to use this tool (for Fukui indices calculations to predict molecular reactivity), but doesn't explicitly state when not to use it or name specific alternatives among the sibling tools. It implies usage for reactivity analysis but lacks explicit exclusions or comparisons to other workflow submission tools.

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