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

With no annotations, the description carries the behavioral burden. It adds important context: outputs are meant for relay to a human decision-maker and not for autonomous administration, and slug/alias matching is case-insensitive. This gives the agent meaningful guidance beyond the schema, though it does not explicitly state lack of side effects.

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 two sentences with no filler. The core lookup behavior is front-loaded, followed by a useful caveat about usage context. Every sentence contributes.

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 single-parameter read-style tool with an output schema, the description is complete: it specifies the input forms, case-insensitivity behavior, and a usage constraint. Nothing critical is missing for an agent to invoke it correctly.

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 coverage for the compound parameter is 100%, so the baseline is 3. The description adds value by clarifying that matching is case-insensitive for slug and alias, which is a useful behavioral detail about how the parameter is interpreted.

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 states a specific verb and resource: it retrieves the 'Full published record for one compound' by identifier. It also distinguishes itself from sibling list/calculation tools by emphasizing a single compound lookup, making its role clear.

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 use when a complete record for a specific compound is needed and gives lookup identifiers, but it does not explicitly state when to prefer this tool over list_compounds, recon_calc, or simulate. Usage is implied rather than directly compared against alternatives.

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