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 does add useful context by stating that every field carries its source page, which helps the agent understand provenance of each value. However, it does not mention whether the substance parameter accepts INN, UNII, CAS, or another identifier, nor what happens if the substance is not found.

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 a single dense sentence that front-loads the core scope ('One molecule') and then lists the included data categories. Every phrase earns its place, with no filler or repetition of the tool name.

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?

The output schema exists and the description enumerates the major output categories, so return-value documentation is not a major gap. The definition is still incomplete because the required parameter is ambiguous and no usage guidance differentiates this tool from closely related siblings, leaving the agent to guess how to invoke it reliably.

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 schema has 0% description coverage for its single required parameter, and the description only says 'one molecule' without explaining what format the substance parameter should take. This is a significant gap because the agent cannot tell whether to pass an INN, UNII, CAS, or some other identifier.

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 identifies the resource as a single molecule and enumerates its content: identifiers, aliases, class, pathway rows, enforcement events, and safety references. It is distinct enough from siblings like get_enforcement_watch and get_safety_label by describing a combined record, though it does not explicitly contrast itself with them.

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 the tool is used when you need a comprehensive substance record with identifiers, pathway, enforcement, and safety data. It does not state when to prefer this over related siblings such as get_safety_label or get_enforcement_watch, nor does it mention any exclusions or context where this tool would be inappropriate.

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