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

With no annotations, the description must fully disclose behavioral traits such as whether it is a read operation, what it returns (e.g., a list of related artists), or any rate/credit implications. The description only mentions billing (1 credit) and provides no behavioral detail, leaving the agent completely uninformed.

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 not effective. It consists of a fragment ('Artist related') plus billing info. It is not structured to convey actionable information; it is under-specified rather than concise. A good description would front-load the action and resource, which this does not.

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?

Despite having only one parameter and no output schema, the description fails to set expectations about the return value or scope. For an 'artist related' endpoint, the user must assume what 'related' means. This is minimal viable at best but actually incomplete because it does not even state whether it returns a list, an object, or how it relates to other 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?

The schema description for 'id' says 'Artist ID', which matches the parameter's purpose. Since schema coverage is 100% and there is only one parameter, the description adds no extra meaning but does not worsen the situation. The baseline of 3 is appropriate because the schema already provides the essential information.

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 says 'Artist related' which is vague and does not specify an action like 'get' or 'list'. It gives a category but not a clear purpose, and it does not differentiate from sibling tools like get_v1_1_artist_albums or get_v1_1_artist_appears_on. The phrase 'Group: Artists' is metadata, not a functional description.

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 on when to use this tool versus the many sibling artist endpoints. The description contains no context about typical use cases, prerequisites, or situations where an alternative would be more appropriate.

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