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

With no annotations, the description carries the full burden. It discloses that the tool takes no arguments and explicitly constrains output usage to human decision-making, not autonomous administration. It implies a read-only listing operation, though it does not explicitly state side-effect freedom or data source.

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, well-structured sentence that front-loads the action and output fields, then adds the no-arguments fact and the usage constraint. Every clause earns its place; there is no redundancy or filler.

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 zero-parameter listing tool with an output schema present, the description is complete. It specifies scope ('every published compound'), key output attributes, that no arguments are needed, and how the results should be used. Nothing essential 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?

There are zero parameters and the schema already reflects this with an empty properties object. The description reinforces this by stating 'Takes no arguments,' which is helpful for an agent scanning quickly. Baseline 4 is appropriate for a no-parameter tool.

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 uses a specific verb ('List') and resource ('every published compound'), and enumerates the exact fields returned: class, terminal half-life, administration routes, and reconstitution math availability. This clearly distinguishes it from siblings like get_compound (single lookup), recon_calc (calculation), and simulate (modeling).

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 gives clear context: outputs are for relay to a human decision-maker and not for autonomous administration. This is an explicit when-not-to-use for autonomous actions, though it does not name alternative tools or specify when to prefer this over siblings.

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