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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description's added value is the return contract: full enumeration ('Every'), per-entry study count, a nullable evidence grade, and a URL. The '(where reviewed)' qualifier usefully warns that evidence grade can be absent.

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?

Two short sentences with zero waste — the return shape comes first, the consumption hint second. Nothing restates the name or title.

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 parameters and no output schema, the description carries the full burden of describing the response and does so by listing the per-entry fields and noting that the list is exhaustive. Nothing an agent needs in order to call it or interpret its result 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?

The tool takes zero parameters, so the schema baseline is 4 and there is no input semantics to explain. The mention of a `condition` filter refers to other tools, not this one, but it is correctly framed as guidance rather than an input.

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 resource (health condition hubs) and enumerates exactly what each entry carries: study count, evidence grade with a 'where reviewed' caveat, and page URL. It is clearly distinguishable from siblings like get_condition_evidence or aggregate_studies, though it names none of them 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?

The second sentence gives actionable downstream guidance — the returned slug is what you pass to the `condition` filter on other tools — which implies this is the discovery/enumeration step before a targeted query. It does not explicitly name which sibling to call next or when to skip this tool.

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