Get an artist

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

The annotation readOnlyHint: true already indicates a safe read operation. The description adds useful behavior context by specifying the returned data (bio, identifiers, platform links), which goes beyond annotations. No contradictions. Slightly lacking detail on auth or error handling, but adequate given the simple nature.

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 a single sentence of 10 words, concise and front-loaded with the action and object. No extraneous information; every word earns its place.

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 simple retrieval tool with one parameter, annotations, and no output schema, the description adequately covers the purpose and return fields. It lacks detail about error responses or required authentication, but these are partially inferred from the readOnlyHint annotation and typical API behavior.

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 the description must compensate. It explicitly mentions 'by id', which directly references the parameter and clarifies its role. However, it does not explain the integer format or constraints beyond what the schema provides. The mention adds minimal but meaningful value.

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 'Retrieve one artist by id' with a specific verb and resource, and distinguishes it from sibling tools like list_artists and update_artist. It also specifies the included fields (bio, identifiers, platform links), leaving no ambiguity.

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 implies usage for retrieving a single artist by ID, but does not explicitly contrast with alternative tools like list_artists or provide when-not-to-use guidance. The context is clear but lacks explicit differentiation or exclusions.

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