Rowan MCP Server

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 effectively describes the tool's behavior: it converts identifiers to SMILES, handles various input types, includes a fallback mechanism, returns SMILES or error messages, and provides examples of successful conversions. It lacks details on rate limits, authentication needs, or error handling specifics, but covers core functionality well.

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, context, returns, examples) and uses bullet points for readability. It is appropriately sized but includes some redundancy (e.g., repeating parameter info from the schema). Most sentences add value, such as explaining the tool's role in workflows and listing input types.

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, no annotations, and an output schema (implied by 'Returns' section), the description is complete. It covers purpose, parameters, usage context, return values, and examples. The output schema handles return format details, so the description need not elaborate further, making it sufficient for effective use.

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 thoroughly. The description adds minimal value beyond the schema: it repeats the parameter descriptions in the 'Args' section and provides examples of 'molecule_name' inputs. No additional syntax, format, or constraints are explained, meeting the baseline for high schema coverage.

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: 'Convert molecule names to SMILES using Chemical Identifier Resolver (CIR).' It specifies the verb ('convert'), resource ('molecule names'), and output format ('SMILES'), and distinguishes it from siblings like 'validate_smiles' (which validates rather than converts) and 'batch_molecule_lookup' (which handles multiple inputs).

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: 'enables natural language input for molecules by converting common names, IUPAC names, CAS numbers, and other identifiers to SMILES strings that can be used with Rowan workflows.' It lists supported input types and includes examples. However, it does not explicitly state when not to use it or name alternatives like 'validate_smiles' for already-known SMILES strings.

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