list_assays_for_aop

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond them: results are derived from linked stressor chemicals plus CompTox bioactivity, and empty results are accompanied by diagnostics rather than being silently empty. It stops short of describing pagination or the shape of those diagnostics.

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 dense sentence with the scope front-loaded and no filler. It is efficient, though the trailing 'with diagnostics explaining empty results' clause is slightly dangling and could be tightened.

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 annotations cover safety. The remaining gaps are meaningful: two of three parameters are undocumented anywhere and the crowded sibling space is not disambiguated, leaving an agent with open questions about both invocation and tool selection.

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 0%, so the description carries the full burden, and it does not deliver: limit and min_hitcall (a domain-specific hit-call threshold defaulting to 0.9) are never explained, and the bioactivity mention does not clarify what min_hitcall filters. Only aop_id is implicitly covered by 'for one AOP'.

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?

Specific verb (list) plus resource (assay candidates) and scope (one AOP), with the underlying mechanism named (linked stressor chemicals, CompTox bioactivity). The singular 'one AOP' implicitly separates it from the plural sibling list_assays_for_aops, but no sibling is named explicitly, so the agent must still infer the boundary against get_assays_for_aop and list_assays_for_query.

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 never states when to choose this over the many near-duplicate siblings (get_assays_for_aop, list_assays_for_aops, get_assays_for_aops, list_assays_for_query). It hints at context by scoping to 'one AOP' and mentioning empty-result diagnostics, but there is no explicit when-to-use, when-not, or alternative routing.

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