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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered. The description adds genuinely useful context about provenance – that `verification` is a carried-through raw-count recomputation proving the percentage was checked against the paper rather than copied from an abstract – though it says nothing about filtering or pagination behavior of the call itself.

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 tool's core scope is stated in the first clause and the verification explanation follows. The second paragraph is longer than strictly necessary but its content is non-obvious and earns space; there is little filler.

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 no output schema and zero schema descriptions, the description should explain more of the contract. It illuminates one returned field (`verification`) well, but leaves the four input parameters, the 40-row default limit, and the shape of the rows unexplained.

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, yet it never mentions drug, ae_type, limit, or the default of 40. Only 'by trial' loosely gestures at the `trial` parameter; the filtering and paging parameters are entirely undocumented.

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 names a specific resource and scope: adverse-event rates broken out by trial and arm, which is clearly distinct from compare_efficacy and get_trial. It lacks an explicit verb (retrieval is only implied by the title), but an agent can tell what data comes back.

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 call this versus compare_efficacy or get_trajectory, and no note on when the rate data is preferable to the trial-level tool. Usage must be inferred entirely from the resource name.

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