get_exposure_list_presence

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds nothing beyond that — no note on scope, data source, or what 'list presence' records contain — so it earns no credit for behavioral 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?

It is a single short sentence with no bloat and the resource is front-loaded, but the brevity reflects under-specification rather than economy of expression. There is nothing to trim because there is almost nothing there.

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 values need not be described, but for a domain-specific exposure tool the description never explains what list-presence data represents or how it differs from the batch and tags siblings. Given the large sibling set, this leaves a real selection 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?

Schema description coverage is 100% with a single documented parameter (dtxsid = DSSTox Substance Identifier), so the baseline of 3 applies. The description adds no meaning beyond the schema, such as whether the identifier is validated or what happens for unknown IDs.

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 'Retrieve list presence data' essentially restates the tool name get_exposure_list_presence in different words, adding no specificity about what 'list presence' means. It also fails to distinguish this from siblings batch_get_exposure_list_presence or list_exposure_list_presence_tags.

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 the batch variant or the tags-listing sibling that an agent must choose between. The agent is left to infer selection criteria entirely 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.