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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, covering safety. The description adds data-quality details (nullable mbid, verified spotify_id) and the ability to supply one of three identifiers, which is useful. However, it does not disclose any potential limitations, such as response size, rate limits, or failure modes. It adds some context beyond annotations but not extensive behavioral insight.

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 three concise sentences with no wasted words. It front-loads the core purpose, then specifies the parameter options, and ends with illustrative use cases. Each sentence contributes distinct value, and the structure is easy to scan.

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 tool with three optional parameters and no output schema, the description covers the main action, the acceptable identifiers, and when to use it. It also lists the response content (profile, mbid, spotify_id, dates, history). It doesn't mention error handling or edge cases, but given the simplicity and annotation coverage, it is sufficiently complete for an agent to call correctly.

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% for each parameter, so the baseline is 3. The description adds the crucial insight that artist_id, slug, or name are interchangeable alternatives ('Provide artist_id, slug, or name'), which is not explicitly stated in the schema. This clarifies that any one of them is sufficient, adding meaning beyond the individual parameter descriptions.

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 clearly states the action: 'Get one artist's profile' and lists specific data fields (nullable mbid, verified spotify_id, upcoming dates, recent history). It includes example queries ('Tell me about Tale of Us') that ground the purpose. It distinguishes from siblings by focusing on a single artist's profile rather than events or listings, though it doesn't explicitly name alternatives.

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 description provides concrete usage examples ('Use this to answer...') that illustrate when to invoke it. It implies the tool is for retrieving artist profile information, but does not explicitly state when not to use it or mention alternative tools like get_artist_events. The guidance is clear but lacks explicit exclusion or routing to siblings.

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