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

With no annotations, the description carries the full behavioral disclosure burden. It reveals cost and lack of API key requirement, but says nothing about whether this is a read-only operation, what the response contains, or whether there are any side effects or rate-limit implications.

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 short, but brevity comes at the expense of substance—it omits the core action. The billing sentence is clear but the tool's purpose is under-specified, which is not effective conciseness.

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 tool with one parameter but no output schema and no annotations, the description fails to explain what is returned, what 'discovered on' means, or how the endpoint relates to sibling artist tools. An agent would struggle to know what this call actually does.

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%, and the only parameter 'id' is described as 'Artist ID' with an example. The tool description adds no additional meaning on top of the schema, so the baseline score of 3 applies.

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 is essentially a restatement of the tool name and title ('Artist discovered on') with the addition 'Group: Artists.' It lacks a verb or explicit outcome, so it never states what the tool actually returns or does. Among siblings like artist_appears_on and artist_featuring, this offers no basis for distinguishing the tool.

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?

No guidance is provided about when to use this tool versus the many similar sibling artist endpoints. The billing information ('Agents can pay per call...') describes payment mechanics, not selection criteria or when this endpoint should be preferred over alternatives.

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