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

With no annotations, the description carries the full burden of disclosing side effects or safety. It does not state that the tool is read-only, nor does it mention any potential side effects, rate limits, or authentication requirements, leaving behavior ambiguous.

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 extremely short, but its brevity sacrifices clarity. It does not efficiently communicate purpose or usage, and the minimal structure does not help the agent understand the tool's role.

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?

The description is incomplete for even a simple tool with a single parameter. It does not explain what the output represents, any limitations, or how it differs from related endpoints, leaving the agent with insufficient context to select or invoke the tool correctly.

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 adds no information about the 'artistId' parameter beyond what the schema already provides via its title. Since schema coverage is 0%, the description fails to compensate with any additional context, such as format expectations or usage notes.

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 'v2/Artist concerts' is vague and lacks an explicit verb or resource explanation. It does not clearly state what the tool does beyond implying it relates to artist concerts, making it indistinguishable from similar sibling tools without additional 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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any conditions, prerequisites, or scenarios where this endpoint would be preferred over other artist-related tools.

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