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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value by disclosing the shape of the payload (four distinct sections of artist data), which matters because there is no output schema. It says nothing about ordering, truncation, or missing-artist behavior.

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 sentences, zero waste: the returned content is front-loaded, then the accepted input forms follow. Nothing is repeated from the schema or annotations.

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, the description carries the burden of describing the return value and does so by naming all four sections. For a two-parameter read tool whose safety is fully annotated, that is nearly complete; only the effect of track_limit on the results is left implicit.

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 baseline is 3, but the description goes beyond the schema's terse 'Catalog id or lowercase hyphenated name' by supplying real examples ('sirusho', 'aram-asatryan') that show the exact accepted format. It does not explain what track_limit governs (the best-known songs list), leaving that to the schema.

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 enumerates exactly what the call returns — profile, best-known songs, discography (albums, singles, compilations, appearances) and related artists — which makes the resource unambiguous and distinguishable from list_artists or get_album. It never states an explicit verb, relying on the tool name to carry the action, so it falls just short of a 5.

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?

It routes the agent to the correct input source by naming search_catalog as the origin of catalog ids, and gives concrete name examples in place of an id. It does not state when to prefer this over a sibling like list_artists or similar_tracks, so there is context but no explicit exclusions.

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