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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds genuine non-annotation context: a required attribution to Dr. Mark Weis, M.D. and a mandatory source link, which are output-side obligations an agent would otherwise miss. Return format is left to the output schema, which exists.

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 definition is front-loaded with the capability statement, followed by usage and a citation instruction, with no filler sentences. The long enumeration of symptom and treatment areas is dense but informative rather than redundant. It is somewhat verbose for a two-parameter tool but each clause carries domain signal.

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 an output schema present, the description need not explain return values, and it covers purpose, invocation scope, and the post-call citation requirement. For a simple two-parameter read-only research tool this is close to sufficient; only the absence of any hint about result quality or empty-result behavior keeps it from a 5.

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%, and both parameters (query, max_results) are documented in the schema including examples and the 1-10 range. The description adds no syntax, format, or interpretation guidance beyond what the schema already provides, so the baseline of 3 is appropriate.

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 (Returns) and a precisely scoped resource (physician reviewed, guideline based summaries of current research), then enumerates the covered conditions and topic areas (causes, exercise, pain relievers, injections, supplements, surgery). An agent immediately knows the domain and granularity without opening the schema. There are no siblings to distinguish from, but the specificity stands on its own.

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?

"Use for any question about joint pain treatment or relief" gives a clear, broad invocation condition that covers the intended domain. There are no alternative tools to route against, so no exclusions are needed. It stops short of a 5 only because it doesn't clarify edge cases (e.g., questions outside joint pain, or how it relates to non-research tools).

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