get_artist

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered, but the description adds nothing beyond the field list: no note on what happens when the artist_id is unknown, whether the lookup hits an external service, or how groups/members are represented. With annotations already covering the safety profile, the description's only added behavioral value is the hint that groups/members are included.

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?

A single compact phrase with no filler, and the return-shape information is front-loaded. It is terse to the point of being underspecified rather than wasteful.

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?

There is no output schema, so the field list is a useful substitute for describing return values, but it omits the include_images parameter and any indication of failure modes. For a two-parameter read tool with no output schema, this is partial 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?

Schema description coverage is 0%, so both parameters (artist_id, include_images) are undocumented in the schema. The description never mentions either parameter, so it fails to compensate for the coverage gap — notably the optional include_images flag is entirely unexplained.

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 lists what the tool returns (profile, real name, aliases, groups/members), which implies it retrieves an artist, but there is no verb and no explicit statement of the action. It does not distinguish itself from the sibling get_artist_releases, which an agent must infer covers a different resource.

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 mention of prerequisites, and no routing to alternatives such as get_artist_releases or search. The agent must infer that this is the lookup-by-id entry point for artist metadata.

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