get_exposure_functional_use

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that – no hint about data source, coverage, or what 'reported' means as opposed to modeled or predicted use, which is the kind of context that would earn credit here.

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?

A single front-loaded sentence with zero padding, which is appropriate for a simple lookup. It is efficient, though its brevity is more a symptom of under-specification than of disciplined editing.

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?

An output schema exists, so return-value explanation is not required, and the annotations carry the behavioral profile. Still, given the dense cluster of functional-use siblings, the description is too thin to let an agent confidently choose and scope this call.

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?

Only one parameter (dtxsid) and schema description coverage is 100%, with the schema itself labeling it 'DSSTox Substance Identifier'. The description adds no meaning beyond the schema, so the baseline 3 applies.

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?

States a clear verb ('Retrieve') and resource ('functional use data'), so the basic purpose is legible. However, it does nothing to distinguish itself from several close siblings such as get_exposure_ccd_functional_use, batch_get_exposure_functional_use, get_exposure_functional_use_probability, and list_exposure_functional_use_categories. An agent cannot tell from the description which functional-use endpoint is the right one.

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 offers no when-to-use guidance, no prerequisites, and no mention of alternatives. With four sibling tools covering functional-use-adjacent data, the absence of routing guidance is a real gap. Usage has to be inferred entirely from the name.

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