get_artist

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context around autocorrect fixing misspellings and username-scoped playcounts, but does not disclose behavior such as precedence when both artist and mbid are supplied or error behavior for unknown artists.

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 compact: a one-line purpose summary followed by a tight Args list. Every sentence adds value and the key constraint about artist/mbid is front-loaded. No filler or repetition.

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 metadata getter with an output schema and annotations already present, the description covers the parameters and the shape of the returned data well. It is missing only light usage guidance that would help an agent decide between this and sibling artist endpoints.

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 0%, but the Args block fully compensates: every parameter gets an explanation, and the crucial semantic that artist is required unless mbid is given is stated. This adds meaning the bare nullable schema cannot convey.

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 ('Get') and resource ('artist metadata'), and enumerates the returned fields (listeners, playcount, similar artists, bio). This clearly distinguishes it from sibling artist endpoints like get_artist_top_tracks, get_artist_tags, or get_artist_correction by scope of metadata.

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 explicit when-to-use or when-not-to-use guidance and no named alternatives. An agent must infer from 'artist metadata' that this is for core profile data rather than artist charts or tags; no exclusions or prerequisites are provided.

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