smiles_max_common_substructure

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

No annotations are provided, and the description does not disclose any behavioral traits such as computational cost, return format, error cases, or prerequisites. The burden is entirely on the description, which fails to add transparency beyond the tool's name.

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 very concise (one sentence), which is good, but it is under-specified. It does not structure information (e.g., input, output) and leaves the user guessing. Every sentence should earn its place, but this one lacks crucial details.

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 simplicity (one parameter, no annotations), the description is incomplete. It does not mention the output schema (though available), the required input format, or any nuances. A complete description for such a tool would include what it returns and example usage.

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 0%, so the description must compensate. It does not mention the parameter 'mols' (an array of SMILES strings) at all. The phrase 'between SMILES' vaguely implies multiple inputs but lacks explicit parameter guidance.

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 verb 'Find' and the resource 'maximum common substructure' and specifies it operates on 'SMILES'. However, it does not mention what the output is (e.g., a SMILES string of the substructure), which would improve clarity.

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?

There is no guidance on when to use this tool versus siblings like 'smiles_has_substructure' (which checks for a single substructure) or other SMILES tools. No when-to-use or when-not-to-use information is provided.

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