Artist profile

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

There are no annotations, so the description carries full responsibility for behavioral disclosure. It does state the tool is a lookup that returns 'recent albums and singles' in a single call, implying a read-only operation, but it does not describe response format, ordering, pagination, or whether any auth is needed.

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?

One sentence, front-loaded with the verb and object, with the qualifier 'in one call' at the end. No filler or redundancy.

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 simple one-parameter schema and no output schema, the description adequately conveys the tool's main purpose and return shape. It could be more specific about what 'recent' means and the structure of returned albums/singles, but the essentials are present.

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 single 'name' parameter is already fully described in the schema ('Artist name to search for'), and the description only restates 'by name' without adding syntax, normalization, or fuzzy-matching details. With 100% schema coverage, the description adds no essential parameter semantics beyond the schema.

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 uses a specific verb ('look up') and resource ('artist by name'), and specifies the return content ('catalogue - recent albums and singles'). However, it does not explicitly contrast itself with siblings like search_catalog, so an agent must infer the boundary from context.

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?

It implies usage when a caller needs an artist's discography but provides no explicit when-to-use/when-not-to-use guidance and no references to alternative tools. No exclusions or conditions are stated, leaving the choice to inference.

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