batch_get_exposure_httk

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no batch-size behavior, no partial-failure handling for bad DSSTox IDs, no rate-limit or ordering context.

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 four-word phrase is front-loaded and wastes nothing, but it is terse to the point of being under-specified rather than genuinely concise. There is no second sentence to earn its place because none exists.

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?

Complexity is low (one array parameter) and an output schema exists, so return values need not be explained. Still, for a batch endpoint, the absence of any note on batch sizing or partial failures leaves a small but real gap.

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 is a single parameter at 100% schema description coverage ('List of DSSTox Substance Identifiers'), so the schema fully documents it. The description adds no semantics such as maximum list length, ID format expectations, or behavior on unresolvable identifiers, 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 verb (fetch), a scope modifier (batch) and a resource (HTTK data), which does implicitly distinguish it from the single-item sibling get_exposure_httk. However, 'HTTK data' is an unexplained acronym and the description never says what kind of data is returned, so the purpose is only vaguely conveyed.

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 when-to-use guidance, no mention of the singular sibling get_exposure_httk as the alternative for non-batch calls, and no preconditions or batch-size limits. An agent must infer the routing decision entirely from the 'batch' prefix in the name.

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