get_bioactivity_aed

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety and idempotency profile is fully covered. The description adds no behavioral context beyond the name — no note on scope, pagination, data provenance, or what the AED dataset contains, so it contributes essentially nothing on top of structured fields.

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?

One short, front-loaded sentence with no filler or redundancy. It is efficient, though its brevity borders on under-specification rather than tight conciseness.

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, and a single-param read tool carries a light burden. Still, with ~100 sibling tools and several bioactivity variants, the description lacks the routing context an agent needs to pick this one 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?

Schema description coverage is 100% ('DSSTox Substance Identifier'), so the schema fully documents the single required parameter. The description adds no syntax or format guidance beyond that, which is the expected baseline when the schema does the heavy lifting.

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 specific verb ('Retrieve') and resource ('Activity Exposure Distribution (AED) data') with the target entity ('for a chemical'), and even expands the acronym. However, it does nothing to distinguish itself from close siblings like get_bioactivity_data or batch_get_bioactivity_aed, leaving the agent to guess which retrieval route to take.

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 statement of when to use this tool versus alternatives, no prerequisites beyond the implied dtxsid, and no indication of when-not to use it. In a sibling set with get_bioactivity_data, get_bioactivity_summary_by_dtxsid, and batch_get_bioactivity_aed, this omission forces inference.

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