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 without the description. The description adds nothing beyond that — no note on what the HTTK payload contains, whether a missing DTXSID errors or returns empty, or any caveats.

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 sentence is short and front-loaded but does no work — it conveys no information beyond the tool name, so it is under-specified rather than genuinely concise. This matches the LOW-tier pattern where brevity reflects missing content, not efficiency.

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?

With one simple parameter, an output schema, and full annotations the structured metadata covers most of the interface, but the description leaves the agent unable to tell what HTTK output is or when this tool beats search_httk or batch_get_exposure_httk. For a tool sitting in a large exposure/httk family, that routing information is the missing piece.

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 description coverage is 100% and the single dtxsid parameter is fully documented as "DSSTox Substance Identifier", so the schema carries the load. Per the baseline rule for high coverage, 3 is appropriate; the description adds no format hints or examples beyond what the schema already states.

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?

"Retrieve HTTK data" essentially restates the tool name and title without saying what HTTK data means, what entity it is keyed on, or how it differs from the sibling search_httk and batch_get_exposure_httk. An agent cannot distinguish this from its siblings without opening the schema.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as search_httk (search) or batch_get_exposure_httk (multiple IDs). The single-ID vs. batch distinction is left entirely to inference from the tool name.

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