statsfm_catalog_artist

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

The verb 'look up' implies a read-only operation, but the description does not explicitly state that there are no side effects, nor does it mention authentication requirements, rate limits, or potential failures. Since no annotations are provided, the description carries the full burden but only partially discloses behavior.

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, concise sentence that conveys the essential purpose without extraneous details. It is well-structured and immediately understandable.

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?

There is no output schema and the description does not specify what the return value contains (e.g., artist details, metadata, or any response format). It also lacks information about possible errors, edge cases, or the context in which this lookup is useful, leaving the agent with limited understanding of the expected result.

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?

Both parameters (artist_id and response_format) are documented in the schema with descriptions, so schema coverage is complete. The tool description adds no additional meaning beyond what the schema already provides, thus it meets the baseline but does not exceed it.

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 the verb 'look up' and the resource 'artist in the stats.fm catalog', which distinguishes it from similar tools like get_artist that may target a different catalog. The phrase 'by id' also specifies the input method, making the purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives such as get_artist, search_artists, or other artist-related lookup tools. There is no mention of scenarios or prerequisites, leaving the selection entirely to the agent's inference.

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