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

No annotations are present, so the description carries the full behavioral burden. "Hosted JS library version + assets" weakly suggests a read-only lookup, but it does not disclose query behavior, empty-input behavior, authentication needs, or side effects.

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 description is short and front-loaded, but it is under-specified rather than appropriately concise. The "cdnjs:" prefix repeats the title, and the remaining fragment gives no action or usage detail.

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 the description does not need to enumerate return values. Still, it lacks the core action, parameter semantics, and selection context needed to invoke the tool correctly, especially given zero annotations and zero schema description coverage.

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 schema exposes only q with a default of "" and no description, so the prose must explain the parameter. The description never mentions q, its format, or that it is the JS library name/search term; the connection is only weakly inferable from the word "library."

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 identifies the resource (cdnjs) and a loose subject area ("Hosted JS library version + assets"), so it is more informative than a pure tautology. However, it omits any verb, leaving unclear whether the tool searches, fetches, lists, or resolves something.

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 when-to-use guidance, no exclusions, and no alternative tool referenced. The only selection hint is the cdnjs domain name itself, which implies a JS-library lookup but does not explain when to prefer this tool over siblings.

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