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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real context beyond that by spelling out the aggregation output shape (subject-type split, RCT/participant counts, publication years, data coverage, strongest studies), which is valuable given there is no output schema.

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 front-loaded sentence with the purpose stated first, followed by a dense but purposeful enumeration of returned metrics. No filler, though the catalog-style list of output facets is long enough to approach the edge of readability.

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?

For a read-only 3-parameter aggregate with no output schema, the description covers what an agent needs to know about the response content. It stops short of covering behavior for an unknown/ambiguous condition or how large the returned payload is, but nothing critical is missing.

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 coverage is 100%, so the baseline is 3; the schema already documents condition, subject enum, and top_studies with defaults and bounds. The description hints at the subject filter ('human vs animal vs in-vitro') and top_studies ('strongest studies') but adds no syntax or behavior beyond those field labels.

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-and-resource framing: it produces an 'evidence profile' for a named health condition hub, then enumerates the profile contents (study counts, subject mix, RCT/participant counts, outcomes, delivery, years, coverage, top studies). This clearly separates it from get_study and search_studies, though it never names a sibling explicitly.

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?

Usage is only implied: you call it when you want an aggregate profile for a condition. There is no statement of when to prefer compare_evidence or aggregate_studies, nor any prerequisite note in the description itself (the 'see list_conditions' hint lives in the schema, not the description).

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