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 and does well by explaining what the tool does (submits a workflow for pKBHX prediction), mentions resource constraints (max_credits parameter), provides context about hydrogen bond basicity importance, and shows return type. However, it doesn't disclose execution time, error conditions, or authentication requirements that would be helpful for an agent.

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, explanation, Returns, Examples) and appropriately sized. However, the Args section largely duplicates schema information, and the hydrogen bond basicity explanation paragraph could be more tightly integrated with the tool's purpose rather than appearing as a separate educational note.

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 workflow submission tool with 6 parameters, 100% schema coverage, but no annotations or output schema, the description provides good context: clear purpose, parameter examples, return type indication, and practical examples. It could improve by explaining workflow states, error handling, or how to retrieve results using sibling tools like retrieve_workflow.

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 parameters thoroughly. The description adds minimal value beyond the schema through the Args section that mostly repeats schema information, though it provides helpful examples showing parameter usage in context. 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 specific action ('submit a hydrogen bond basicity workflow'), the resource ('to predict pKBHX values'), and distinguishes it from siblings by focusing on hydrogen bond basicity prediction rather than other computational chemistry workflows like ADMET, docking, or pKa calculations listed among siblings.

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 implied usage through examples showing different scenarios (basic prediction, with conformer search/optimization, for drug molecules), but lacks explicit guidance on when to use this tool versus alternatives like other workflow submission tools or when not to use it. No direct comparison to sibling tools is provided.

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