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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description 'Get Artist name' doesn't reveal any behavioral traits—it doesn't mention whether this is a read-only operation, what authentication might be required, potential rate limits, error conditions, or what the response format looks like. For a tool with zero annotation coverage, this is completely inadequate.

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?

While the description is brief with just two words, this represents under-specification rather than effective conciseness. The text doesn't earn its place by providing useful information—it's too sparse to be helpful. A truly concise description would still convey essential purpose and context efficiently, which this fails to do.

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?

Given the tool's purpose (retrieving artist information) with no annotations and no output schema, the description is completely inadequate. It doesn't explain what the tool returns, how results are formatted, or any behavioral aspects. For a data retrieval tool, this leaves critical gaps that would hinder an AI agent's ability to use it effectively.

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?

The description provides no information about parameters, but the input schema has 100% description coverage with a single parameter 'method' documented as 'Get or post request'. Since schema coverage is high, the baseline score is 3. The description doesn't add any value beyond what the schema already provides, but it also doesn't detract from the existing documentation.

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 'Get Artist name' is a tautology that essentially restates the tool name 'get_artist' with minor variation. It doesn't specify what resource is being retrieved (e.g., artist information from a database, API, or service) or provide any meaningful context about the operation. While it includes a verb ('Get'), it lacks specificity about what exactly is being obtained beyond the obvious from the name.

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 are no usage guidelines provided in the description. It doesn't indicate when to use this tool, what prerequisites might be needed, or any alternative approaches. With no sibling tools mentioned, the absence of guidance is still problematic as it leaves the agent without context for proper tool selection.

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